Skip to content

chore(release): 0.46.0#440

Merged
rhuanbarreto merged 1 commit into
mainfrom
release
Jul 3, 2026
Merged

chore(release): 0.46.0#440
rhuanbarreto merged 1 commit into
mainfrom
release

Conversation

@archgatebot

@archgatebot archgatebot Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

archgate

0.46.0 (2026-07-02)

⚠ BREAKING CHANGES

Features

  • session-context: per-editor list/show subcommands; remove --skip and its false premise (#446) (dd96230)

Bug Fixes

  • ci: read POSTHOG_PROJECT_ID from secrets, not vars, in release annotation (#443) (a53b305)
  • detect opencode Desktop app installs, not just the CLI (#439) (ed92b2b)
  • hooks: force bash shell for WorktreeCreate hook on Windows (#442) (9da86cf)
  • release: cap breaking-change bumps to minor while pre-1.0 (#447) (3df6c91), closes #446 #440 #440 #440
  • repair broken WorktreeCreate hook and add PR approval policy (#441) (de5e97d)
  • session-context: select top-level opencode sessions, add --root flag (#445) (29b13f4)

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"
  }
}
```

Access Restrictions

The command 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
  • JSON must be valid, otherwise the command will be ignored
  • Parameters apply only to the current release execution
  • The command can be updated by editing the comment or adding a new one

@archgatebot archgatebot Bot requested a review from rhuanbarreto as a code owner July 1, 2026 14:04
cursor[bot]
cursor Bot previously approved these changes Jul 1, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved: mechanical release bump to 0.45.8 (version strings and changelog only). Cursor Bugbot was not present on this PR, so that signal was skipped; no additional reviewers assigned—rhuanbarreto is already requested.

Open in Web View Automation 

Sent by Cursor Approval Agent: Archgate CLI Approver

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 1, 2026

Copy link
Copy Markdown

Deploying archgate-cli with  Cloudflare Pages  Cloudflare Pages

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

View logs

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Code Coverage

Metric Value
Lines 90.0% (7173 / 7971)
Threshold 90% minimum — met
Platforms Linux + Windows

Full HTML report available in workflow artifacts.

Per-directory breakdown
Directory Coverage Lines
src/commands/ 88.5% 1984 / 2243
src/engine/ 90.9% 1463 / 1610
src/formats/ 100.0% 142 / 142
src/helpers/ 90.1% 3584 / 3976

@archgatebot archgatebot Bot force-pushed the release branch 4 times, most recently from cc43193 to a70df36 Compare July 2, 2026 08:47
@archgatebot archgatebot Bot changed the title chore(release): 0.45.8 chore(release): 1.0.0 Jul 2, 2026
rhuanbarreto added a commit that referenced this pull request Jul 2, 2026
## Problem

The session-context breaking changes (#446) made simple-release propose
**v1.0.0** (release PR #440). We are not ready to publish 1.0.0 — the
project still ships no support guarantees. Pre-1.0, breaking changes
should produce a **minor** bump (0.46.0).

## Fix

Override `getNextVersion` in `.simple-release.js`: when the current
version is `0.x` and the conventional-commit computation yields a major
bump, return the next minor instead. `bump()` derives its version from
`getNextVersion`, so the manifest writes, changelog, release-PR title,
and tag all stay consistent from the single cap.

Explicit `version`/`as` bump options bypass the cap, so v1.0.0 remains
available as a deliberate, forced decision.

## Verification

Dry-run against the live git history (which contains the `feat!`
commits):

| | computed next version |
|---|---|
| stock `NpmProject` | `1.0.0` |
| capped `ArchgateProject` | `0.46.0` |

Lint, typecheck, format, and `archgate check` (39/39) green.

## After merge

The push to `main` re-triggers the release `pull-request` workflow,
which updates release PR #440 in place from 1.0.0 to 0.46.0 (title,
changelog, version files, shim versions). **Do not merge #440 before
this lands.**

https://claude.ai/code/session_01SGjSjrywTnZDcUqgHWGrTj

Signed-off-by: Rhuan Barreto <rhuan@barreto.work>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@archgatebot archgatebot Bot changed the title chore(release): 1.0.0 chore(release): 0.46.0 Jul 2, 2026
@rhuanbarreto rhuanbarreto merged commit 417c093 into main Jul 3, 2026
39 of 49 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