Repository navigation
chore(release): 0.55.0 - #575
Merged
Merged
Conversation
Deploying archgate-cli with
|
| Latest commit: |
f1efc71
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b05ab0de.archgate-cli.pages.dev |
| Branch Preview URL: | https://release.archgate-cli.pages.dev |
Contributor
Code Coverage
Full HTML report available in workflow artifacts. Per-directory breakdown
|
archgatebot
Bot
force-pushed
the
release
branch
3 times, most recently
from
August 21, 2026 17:44
5898fbb to
2f65b15
Compare
rhuanbarreto
previously approved these changes
Aug 21, 2026
archgatebot
Bot
force-pushed
the
release
branch
3 times, most recently
from
August 21, 2026 20:28
3eec97d to
19958ec
Compare
archgatebot
Bot
force-pushed
the
release
branch
2 times, most recently
from
August 22, 2026 13:29
1cf5c5e to
a452945
Compare
rhuanbarreto
added a commit
that referenced
this pull request
Aug 22, 2026
## What happened Merging #581 did not update the release branch. CI was green, the merge was clean, and the release workflow reported success — but release stayed on the prior commit. The merge fired **two** release runs in the same second: ``` 12:50:14Z cc8d93c event=push CANCELLED — zero jobs ran 12:50:16Z cc8d93c event=issue_comment success — both jobs skipped ``` Both resolve `github.ref_name` to the default branch, so the workflow-level group held both: ```yaml concurrency: group: release-${{ github.ref_name }} cancel-in-progress: false ``` `cancel-in-progress: false` only protects a run already **in progress**. A **pending** run is evicted when a newer one joins the group, so the `issue_comment` run displaced the `push` run before it started a single job. That matters because only the push run releases. Across the last 8 runs, every `issue_comment` run skipped both mutating jobs; the run that cut 0.55.0 was `event=push`: ``` 10:43:40Z 1bd7306 event=push -> Pull request=SUCCESS (cut 0.55.0) 12:50:14Z cc8d93c event=push -> CANCELLED, no jobs ``` It fails silently — no red check anywhere, just a missing release. ## Why it recurs Not a one-off. A bot comments on essentially every merged PR, so any comment landing within seconds of a push to main evicts the release run. ## The fix The group moves from the workflow to the two jobs that actually push the release branch, `pull-request` and `release`. Both keep one shared group, so they stay mutually exclusive with each other. A job gated off by `check` never joins the group, so a no-op comment run has nothing to displace. Two-push ordering is unaffected: if a later merge evicts an earlier pending `pull-request` job, the surviving run is based on a newer main and covers both commits. ## Already remediated separately The lost run for `cc8d93c` was re-run manually, so the release branch is caught up — `a452945 chore(release): 0.55.0` now sits on top of `cc8d93c`, 0 behind main, and #575 carries the changelog entry. This PR prevents the next occurrence. ## Testing Workflow parses; `concurrency` is absent at workflow level and present on both mutating jobs with the shared group. actionlint and zizmor run on this path in CI. --------- Signed-off-by: Rhuan Barreto <rhuan@barreto.work>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
archgatebot
Bot
force-pushed
the
release
branch
from
August 22, 2026 13:42
a452945 to
f1efc71
Compare
rhuanbarreto
approved these changes
Aug 22, 2026
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
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.
archgate
0.55.0 (2026-08-22)
Features
Bug Fixes
This PR was generated with simple-release.
📄 Cheatsheet
You can configure the bot's behavior through a pull request comment using the
!simple-release/set-optionscommand.Command Format
Useful Parameters
Bump
versionstringas'major' | 'minor' | 'patch' | 'prerelease'prereleasestringfirstReleasebooleanskipbooleanbyProjectRecord<string, object>Publish
skipbooleanaccess'public' | 'restricted'tagstringUsage Examples
Force specific version
Force major bump
Create alpha pre-release
Publish with specific access and tag
Custom Changelog Preamble
You can add custom markdown to the top of the changelog (right after the version header) using the
!simple-release/set-preamblecommand. The markdown after the command line becomes the preamble.In a monorepo, pass the full package name after the command to target a single package's changelog. Wrap the name in backticks so GitHub keeps it as text instead of a mention:
Use one comment per package, plus one without a name for the whole release.
Access Restrictions
The commands can only be used by users with permissions:
Notes
!simple-release/set-optionscommand takes priority!simple-release/set-preamblecomment per package takes priorityset-optionscommand will be ignored