Release PR#554
Closed
ryanbas21 wants to merge 1 commit into
Closed
Conversation
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx affected -t build lint test docs e2e-ci --ve... |
❌ Failed | 26m 40s | View ↗ |
nx-cloud record -- nx format:check --verbose |
✅ Succeeded | 4s | View ↗ |
☁️ Nx Cloud last updated this comment at 2025-10-28 14:25:42 UTC
github-actions
Bot
force-pushed
the
changeset-release/develop
branch
from
3eafa12 to
0f23fbc
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to develop, this PR will be updated.
Releases
@forgerock/ping-protect@4.6.1
Patch Changes
a87b517Thanks @ryanbas21! - fix the protect-package versioning. no functional changes to protect package, but allow more loose versioning on javascript-sdk