chore(dev): release 5.3.1-beta.1 - #115
Merged
finalerock44 merged 1 commit intoAug 10, 2026
Merged
Conversation
dcd-cli-release-please
Bot
force-pushed
the
release-please--branches--dev--components--@devicecloud.dev/dcd
branch
from
August 10, 2026 18:00
ed06cd2 to
7d74751
Compare
14 tasks
dcd-cli-release-please
Bot
force-pushed
the
release-please--branches--dev--components--@devicecloud.dev/dcd
branch
2 times, most recently
from
August 10, 2026 18:10
75784f2 to
811c720
Compare
finalerock44
added a commit
that referenced
this pull request
Aug 10, 2026
Retargets the pending dev beta release from 5.2.0-beta.5 to 5.3.1-beta.1. The beta line is still numbered off 5.2.0 because the stable 5.3.0 release never completed: the promote PR (#108) merged with `Release-As: 5.3.0`, but the release-please PR it generated (#109) is still open, so no v5.3.0 tag exists and `.release-please-manifest-beta.json` sat at 5.2.0-beta.4. Release-please therefore proposed 5.2.0-beta.5 (#115) for the flow-discovery fix in #114, which is behind the stable line rather than ahead of it. The stable line is 5.3.0, so the next beta belongs on the 5.3.1 patch series. This commit is intentionally empty — the payload is the footer below, which release-please reads to pin the exact version of the next dev release. It applies once and needs no follow-up cleanup, unlike a `release-as` key in release-please-config-beta.json, which would pin every subsequent dev release until removed. Release-As: 5.3.1-beta.1
dcd-cli-release-please
Bot
changed the title
dcd-cli-release-please
Bot
force-pushed
the
release-please--branches--dev--components--@devicecloud.dev/dcd
branch
from
August 10, 2026 18:13
811c720 to
0b3a694
Compare
finalerock44
deleted the
release-please--branches--dev--components--@devicecloud.dev/dcd
branch
August 10, 2026 18:19
Contributor
Author
|
🤖 Created releases: 🌻 |
dcd-cli-release-please
Bot
added
autorelease: tagged
and removed
autorelease: pending
labels
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.
🤖 I have created a release beep boop
5.3.1-beta.1 (2026-08-10)
Bug Fixes
Dependencies
Miscellaneous
This PR was generated with Release Please. See documentation.