Before the suite's first release candidates (v27.1-rc.1) go out: a pre-release was announced as "released" and "is out".
Now a release with prerelease: true is:
titled <repo> <tag> release candidate;
opened with "is a release candidate: a pre-release for testing, not yet the release. latest and a plain install stay where they are.";
posted to Discord as **<repo> <tag>** release candidate.
A final release is announced exactly as before. I ran announce.sh against a fake curl for both cases and checked the forum payload and the Discord message.
Each repo pins this action by SHA, so the inbuxa repos get a pin bump next.
Before the suite's first release candidates (`v27.1-rc.1`) go out: a pre-release was announced as "released" and "is out".
Now a release with `prerelease: true` is:
- titled `<repo> <tag> release candidate`;
- opened with "is a release candidate: a pre-release for testing, not yet the release. `latest` and a plain install stay where they are.";
- posted to Discord as `**<repo> <tag>** release candidate`.
A final release is announced exactly as before. I ran `announce.sh` against a fake `curl` for both cases and checked the forum payload and the Discord message.
Each repo pins this action by SHA, so the inbuxa repos get a pin bump next.
A pre-release (the suite's v27.1-rc.N tags) was announced as "released"
and "is out". It is now titled "<repo> <tag> release candidate", its first
line says it is a pre-release for testing that leaves latest and a plain
install where they are, and the Discord line says "release candidate".
A final release is announced exactly as before.
Claude-Session: https://claude.ai/code/session_01Y2F7CWRXorttf5sjSbxwpj
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Before the suite's first release candidates (
v27.1-rc.1) go out: a pre-release was announced as "released" and "is out".Now a release with
prerelease: trueis:<repo> <tag> release candidate;latestand a plain install stay where they are.";**<repo> <tag>** release candidate.A final release is announced exactly as before. I ran
announce.shagainst a fakecurlfor both cases and checked the forum payload and the Discord message.Each repo pins this action by SHA, so the inbuxa repos get a pin bump next.