Skip to content

chore(release): 0.55.0 - #575

Merged
rhuanbarreto merged 1 commit into
mainfrom
release
Aug 22, 2026
Merged

rhuanbarreto merged 1 commit into
mainfrom
release

Conversation

@archgatebot

@archgatebot archgatebot Bot commented Aug 20, 2026 •

Copy link
Copy Markdown
Contributor

archgate

0.55.0 (2026-08-22)

Features

  • bun: adopt Bun 1.4 archive, test parallelism, and terminal APIs (#576) (22715ee)

Bug Fixes

  • ci: stop comment runs from evicting the release push run (#585) (9a3c881), references #581 #575
  • fs: survive Bun 1.4's rejecting-read regression, and upgrade to 1.4.0 (#574) (51f7ffc)
  • session-context: report a read failure instead of throwing it (#577) (94ffdcd), references #576 #574 #576
  • session-context: truncate previews on grapheme boundaries (#581) (cc8d93c)

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-options command.

Command Format

!simple-release/set-options

```json
{
  "bump": {},
  "publish": {}
}
```

Useful Parameters

Bump

Parameter Type Description
version string Force set specific version
as 'major' | 'minor' | 'patch' | 'prerelease' Release type
prerelease string Pre-release identifier (e.g., "alpha", "beta")
firstRelease boolean Whether this is the first release
skip boolean Skip version bump
byProject Record<string, object> Per-project bump options for monorepos

Publish

Parameter Type Description
skip boolean Skip publishing
access 'public' | 'restricted' Package access level
tag string Tag for npm publication

Usage Examples

Force specific version

!simple-release/set-options

```json
{
  "bump": {
    "version": "2.0.0"
  }
}
```

Force major bump

!simple-release/set-options

```json
{
  "bump": {
    "as": "major"
  }
}
```

Create alpha pre-release

!simple-release/set-options

```json
{
  "bump": {
    "prerelease": "alpha"
  }
}
```

Publish with specific access and tag

!simple-release/set-options

```json
{
  "bump": {
    "prerelease": "beta"
  },
  "publish": {
    "access": "public",
    "tag": "beta"
  }
}
```

Custom Changelog Preamble

You can add custom markdown to the top of the changelog (right after the version header) using the !simple-release/set-preamble command. The markdown after the command line becomes the preamble.

!simple-release/set-preamble

## What's new?

- The website was completely redesigned
- The new API gives you awesome possibilities

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:

!simple-release/set-preamble `@your-org/core`

## Core changes

- New plugin system

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:

  • repository owner
  • organization member
  • collaborator

Notes

  • The last comment with !simple-release/set-options command takes priority
  • The last !simple-release/set-preamble comment per package takes priority
  • JSON must be valid, otherwise the set-options command will be ignored
  • Parameters apply only to the current release execution
  • The commands can be updated by editing the comment or adding a new one

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 20, 2026 •

Copy link
Copy Markdown

Deploying archgate-cli with  Cloudflare Pages  Cloudflare Pages

Latest commit: f1efc71
Status: ✅  Deploy successful!
Preview URL: https://b05ab0de.archgate-cli.pages.dev
Branch Preview URL: https://release.archgate-cli.pages.dev

View logs

@archgatebot
archgatebot Bot requested a review from rhuanbarreto as a code owner August 20, 2026 22:10
@github-actions

github-actions Bot commented Aug 20, 2026 •

Copy link
Copy Markdown
Contributor

Code Coverage

Metric Value
Lines 99.9% (10624 / 10635)
Threshold 99.9% minimum — met
Platforms Linux + Windows

Full HTML report available in workflow artifacts.

Per-directory breakdown
Directory Coverage Lines
src/commands/ 100.0% 2194 / 2194
src/engine/ 100.0% 2618 / 2619
src/formats/ 100.0% 151 / 151
src/helpers/ 99.8% 5661 / 5671

@archgatebot archgatebot Bot changed the title chore(release): 0.54.1 chore(release): 0.55.0 Aug 21, 2026
@archgatebot
archgatebot Bot force-pushed the release branch 3 times, most recently from 5898fbb to 2f65b15 Compare August 21, 2026 17:44
rhuanbarreto
rhuanbarreto previously approved these changes Aug 21, 2026
@archgatebot
archgatebot Bot force-pushed the release branch 3 times, most recently from 3eec97d to 19958ec Compare August 21, 2026 20:28
@archgatebot
archgatebot Bot force-pushed the release branch 2 times, most recently from 1cf5c5e to a452945 Compare August 22, 2026 13:29
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>
@rhuanbarreto
rhuanbarreto merged commit 47a2ac3 into main Aug 22, 2026
30 of 41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant