[archgatebot]

archgate

0.56.0 (2026-09-07)

⚠ BREAKING CHANGES

• auth: archgate login authenticates against the Archgate
  platform
  via the OAuth device flow instead of GitHub's, so every user signs in
  again
  to obtain a platform session.

  • Signup no longer happens in the CLI. The email, editor and use-case
    prompts
    are gone; registration is whatever the Archgate platform's sign-in
    offers.
  • Credentials are stored as an access/refresh token set under
    auth.archgate.dev, not a single token under plugins.archgate.dev.
  • archgate login writes a
    credential.https://plugins.archgate.dev.helper
    entry to the user's global git config, and archgate login logout
    removes it.
  • archgate credential is a new command, invoked by git rather than by
    users.

  Tokens issued before this change keep working: they remain under
  plugins.archgate.dev and are still returned, so existing sessions are
  not
  invalidated until the user signs in again.

  ---

Features

• auth: log in to the Archgate platform and serve git credentials (#602) (ec154b1)

Bug Fixes

• plugin-install: keep Copilot CLI output out of error logs (#598) (2155ed7), closes #595

---

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]

Deploying archgate-cli with    Cloudflare Pages

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

View logs

[github-actions]

Code Coverage

Metric	Value
Lines	99.9% (10873 / 10883)
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%	2265 / 2265
src/engine/	100.0%	2618 / 2619
src/formats/	100.0%	151 / 151
src/helpers/	99.8%	5839 / 5848