Skip to content

chore(dev): release 5.3.1-beta.1 - #115

Merged
finalerock44 merged 1 commit into
devfrom
release-please--branches--dev--components--@devicecloud.dev/dcd
Aug 10, 2026
Merged

chore(dev): release 5.3.1-beta.1#115
finalerock44 merged 1 commit into
devfrom
release-please--branches--dev--components--@devicecloud.dev/dcd

Conversation

@dcd-cli-release-please

@dcd-cli-release-pleasedcd-cli-release-pleaseBot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

5.3.1-beta.1 (2026-08-10)

Bug Fixes

  • cloud: exclude config-shaped files from flow discovery (#114) (13d01ee), closes#99

Dependencies

  • bump the minor-and-patch group with 5 updates (#112) (2223dd4)

Miscellaneous


This PR was generated with Release Please. See documentation.

@dcd-cli-release-please
dcd-cli-release-pleaseBotforce-pushed the release-please--branches--dev--components--@devicecloud.dev/dcd branch from ed06cd2 to 7d74751CompareAugust 10, 2026 18:00
@dcd-cli-release-please
dcd-cli-release-pleaseBotforce-pushed the release-please--branches--dev--components--@devicecloud.dev/dcd branch 2 times, most recently from 75784f2 to 811c720CompareAugust 10, 2026 18:10
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-pleasedcd-cli-release-pleaseBot changed the title chore(dev): release 5.2.0-beta.5chore(dev): release 5.3.1-beta.1Aug 10, 2026
@dcd-cli-release-please
dcd-cli-release-pleaseBotforce-pushed the release-please--branches--dev--components--@devicecloud.dev/dcd branch from 811c720 to 0b3a694CompareAugust 10, 2026 18:13
@finalerock44
finalerock44 merged commit 57711c6 into devAug 10, 2026
10 checks passed
@finalerock44
finalerock44 deleted the release-please--branches--dev--components--@devicecloud.dev/dcd branch August 10, 2026 18:19
@dcd-cli-release-please

Copy link
Copy Markdown
ContributorAuthor

🤖 Created releases:

🌻

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dcd cloud: --config doesn't exclude other config-shaped files in the same flow folder

1 participant

@finalerock44