deps: Bump System.Security.Cryptography.Pkcs from 8.0.1 to 10.0.1#26
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
Conversation
--- updated-dependencies: - dependency-name: System.Security.Cryptography.Pkcs dependency-version: 10.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Owner
|
Merged into feature/unified-cli-auth branch |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/nuget/src/PPDS.Dataverse/System.Security.Cryptography.Pkcs-10.0.1
branch
27 tasks
joshsmithxrm
added a commit
that referenced
this pull request
Jan 8, 2026
* docs: add Playwright E2E testing for Claude automation to roadmap * docs: add Playwright E2E testing infrastructure design * feat(e2e): implement Playwright E2E infrastructure (Slice 1) - Add Playwright and @vscode/test-electron dependencies - Create e2e directory structure with helpers and smoke tests - Implement VSCodeLauncher helper for Electron-based VS Code launch - Add basic smoke test that launches VS Code and takes screenshots - Add npm scripts: e2e:smoke, e2e:headed, e2e:debug, e2e:report - Configure playwright.config.ts with smoke/integration projects - Exclude e2e from main tsconfig (separate compilation) Slice 1 complete: VS Code launches successfully via Playwright * fix(e2e): address code review feedback - Exclude e2e files from tsconfig.build.json (fixes production build) - Add file-level comment explaining console.log usage in test infrastructure - Improve JSDoc on getVSCodePath() with @returns tag - Expand empty catch block documentation with WHY explanation - Extract magic number to named constant VSCODE_STABILIZATION_DELAY_MS * feat(e2e): implement command palette and webview helpers (Slice 2) - Add CommandPaletteHelper for executing VS Code commands programmatically - Add WebviewHelper for accessing webview panel iframes - Add command execution smoke tests (Solutions, Metadata Browser, Plugin Traces) - Extract verifyCommandExecutes() helper to avoid test duplication - Use named constants for timeout values Slice 2 complete: Commands execute via command palette, 6 tests passing * feat(e2e): add screenshot helper and Claude JSON reporter (Slices 3-4) Slice 3: Screenshot Helper - ScreenshotHelper class for full page, element, and webview screenshots - Automatic directory creation and filename management - Screenshot path tracking for reports - Helper index file for cleaner imports Slice 4: Claude JSON Reporter - Custom Playwright reporter with AI-optimized JSON output - Structured test results with pass/fail status, errors, and suggestions - Pattern-based suggestions (timeout errors, element not found, etc.) - Dual output: human-readable console + JSON file for programmatic parsing All 6 smoke tests passing (29s duration) * feat(e2e): add console log capture for test debugging * feat(e2e): add extension Output channel log capture via getExtensionLogs() * docs: add E2E testing documentation to CLAUDE.md and update FUTURE_ENHANCEMENTS * docs: add E2E testing to CHANGELOG * feat(e2e): add integration tests for Environment Setup and Solutions panels - Add Environment Setup integration tests: form fields, Service Principal auth, save operation - Add Solutions panel integration tests with credential-based skip mechanism - Add e2e:integration and e2e:all npm scripts - Add e2e/README.md with testing documentation and credential setup guide - Update .gitignore to exclude .env.* credential files * feat(e2e): add dotenv support and fix integration tests - Add dotenv to auto-load .env.e2e.local credentials - Add Test Connection step to Solutions setup for credential validation - Increase API wait time to 10s for solutions loading - Fix clickable links test to handle SPA-style href="#" pattern - Add detailed logging for debugging test failures * docs(e2e): add lessons learned and credential setup details * docs: update CHANGELOG with integration tests and dotenv * fix(e2e): address CodeQL security warning and cleanup race condition - Fix incomplete URL substring sanitization (CodeQL High) by using proper URL parsing with hostname validation instead of includes() - Add delay and retry logic for user data directory cleanup to handle VS Code process file locks gracefully * fix(e2e): address code review feedback from Gemini and Copilot - Add publisher ID to extension folder filter for robustness - Update WebviewHelper to support viewType parameter for reliable panel targeting (prevents flaky tests with multiple webviews) - Remove unnecessary fixed timeout after selectOption (let waitForSelector handle it) - Replace fixed 10s timeout with element-based waiting for solutions load - Clear credentials before taking screenshots (security improvement) - Update all getWebviewFrame calls to use specific viewTypes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated System.Security.Cryptography.Pkcs from 8.0.1 to 10.0.1.
Release notes
Sourced from System.Security.Cryptography.Pkcs's releases.
10.0.0-preview.6.25358.103
You can build .NET 10.0 Preview 6 from the repository by cloning the release tag
v10.0.0-preview.6.25358.103and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.5.25277.114
You can build .NET 10.0 Preview 5 from the repository by cloning the release tag
v10.0.0-preview.5.25277.114and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.4.25258.110
You can build .NET 10.0 Preview 4 from the repository by cloning the release tag
v10.0.0-preview.4.25258.110and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.3.25171.5
You can build .NET 10.0 Preview 3 from the repository by cloning the release tag
v10.0.0-preview.3.25171.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.2.25163.2
You can build .NET 10.0 Preview 2 from the repository by cloning the release tag
v10.0.0-preview.2.25163.2and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.1.25080.5
You can build .NET 10.0 Preview 1 from the repository by cloning the release tag
v10.0.0-preview.1.25080.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.112
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.112and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.111
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.111and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.110
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.110and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.109
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.109and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.101
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.101and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.7
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.7and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.6
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.6and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.5
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.4
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.4and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.3
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.3and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.2
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.2and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.1
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.1and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.0and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-rc.2.24473.5
You can build NET 9.0 RC2 from the repository by cloning the release tag
v9.0.0-rc.2.24473.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-rc.1.24431.7
You can build .NET 9.0 RC1 from the repository by cloning the release tag
v9.0.0-rc.1.24431.7and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-preview.7.24405.7
You can build .NET 9.0 Preview 7 from the repository by cloning the release tag
v9.0.0-preview.7.24405.7and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-preview.6.24327.7
You can build .NET 9.0 Preview 6 from the repository by cloning the release tag
v9.0.0-preview.6.24327.7and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-preview.5.24306.7
You can build .NET 9.0 Preview 5 from the repository by cloning the release tag
v9.0.0-preview.5.24306.7and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-preview.4.24266.19
You can build .NET 9.0 Preview 4 from the repository by cloning the release tag
v9.0.0-preview.4.24266.19and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-preview.3.24172.9
You can build .NET 9.0 Preview 3 from the repository by cloning the release tag
v9.0.0-preview.3.24172.9and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-preview.2.24128.5
You can build .NET 9.0 Preview 2 from the repository by cloning the release tag
v9.0.0-preview.2.24128.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.0-preview.1.24080.9
You can build .NET 9.0 Preview 1 from the repository by cloning the release tag
v9.0.0-preview.1.24080.9and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.122
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.122and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.121
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.121and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.120
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.120and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.119
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.119and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.100-preview.1
8.0.18
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.18and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.17
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.17and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.16
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.16and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.15
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.15and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.14
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.14and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.13
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.13and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.12
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.12and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.11
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.11and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.10
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.10and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.8
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.8and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.7
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.7and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.6
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.6and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.5
You can build .NET 8 from the repository by cloning the release tag
v8.0.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.4
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.4and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.3
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.3and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
8.0.2
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.2and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)