jlxq0/jmap-mcp
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases 1 Packages 1 Wiki Activity Actions

chore(release): v0.2.15 #19

Merged
jlxq0 merged 1 commit from release/v0.2.15 into main 2026-08-27 03:17:34 +00:00
Conversation 0 Commits 1 Files changed 3 +14 -2
jlxq0 commented 2026-08-27 03:14:45 +00:00
Owner
Copy link

Version bump for the v0.2.15 tag, plus the second toolchain-resolution route in AGENTS.md.

What v0.2.15 carries

  • tag-ancestry gate on tag builds, both pipelines (#16, closes half of #14)
  • X-Forwarded-For entry-count logging so the ingress chain length can be measured (#18)
  • AGENTS.md corrections: the mirror block is live and yesterday's clearance was wrong (#17), mergeable=true is not the merge gate (#15), annotated-tag rev-parse, and the queued-run/pending-context entry

No behaviour change for users. The only runtime change is one extra info line per authenticated request carrying a count and never the entries.

The toolchain note

With RUSTUP_TOOLCHAIN unset, rust-toolchain.toml pinning 1.93.0 and ci.yml:35 pinning 1.93.0, rustc --version reported 1.98.0 through ~/.local/share/mise/shims/rustc. A local green on the wrong compiler with every visible signal agreeing, and it needs no misconfiguration. clippy::naive_bytecount is the specimen: it fires on 1.93.0 and the shim would have passed the first spelling of xff_entry_count straight to CI.

AGENTS.md documented only the env-var route. Now both.

Gates

All five on 1.93.0: fmt, clippy -D warnings, test (168), audit, deny.

Deploy path

Verified rather than assumed, since I had told Alan the mirror blocked the release and it does not:

.forgejo/workflows/ci.yml   0 matches for ghcr
repo secrets                FORGE_PUSH_TOKEN only, no GHCR_TOKEN
running pod                 forge.oddie.app/jlxq0/jmap-mcp@sha256:316e64a8…
manifest pin                forge.oddie.app/jlxq0/jmap-mcp:v0.2.14@sha256:316e64a8…

Forge registry end to end. The GitHub mirror being blocked lags the public repo and does not touch the deploy.

Version bump for the v0.2.15 tag, plus the second toolchain-resolution route in `AGENTS.md`. ## What v0.2.15 carries - `tag-ancestry` gate on tag builds, both pipelines (#16, closes half of #14) - X-Forwarded-For entry-count logging so the ingress chain length can be measured (#18) - `AGENTS.md` corrections: the mirror block is live and yesterday's clearance was wrong (#17), `mergeable=true` is not the merge gate (#15), annotated-tag `rev-parse`, and the queued-run/pending-context entry No behaviour change for users. The only runtime change is one extra `info` line per authenticated request carrying a count and never the entries. ## The toolchain note With `RUSTUP_TOOLCHAIN` **unset**, `rust-toolchain.toml` pinning `1.93.0` and `ci.yml:35` pinning `1.93.0`, `rustc --version` reported **1.98.0** through `~/.local/share/mise/shims/rustc`. A local green on the wrong compiler with every visible signal agreeing, and it needs no misconfiguration. `clippy::naive_bytecount` is the specimen: it fires on 1.93.0 and the shim would have passed the first spelling of `xff_entry_count` straight to CI. `AGENTS.md` documented only the env-var route. Now both. ## Gates All five on 1.93.0: `fmt`, `clippy -D warnings`, `test` (168), `audit`, `deny`. ## Deploy path Verified rather than assumed, since I had told Alan the mirror blocked the release and it does not: ``` .forgejo/workflows/ci.yml 0 matches for ghcr repo secrets FORGE_PUSH_TOKEN only, no GHCR_TOKEN running pod forge.oddie.app/jlxq0/jmap-mcp@sha256:316e64a8… manifest pin forge.oddie.app/jlxq0/jmap-mcp:v0.2.14@sha256:316e64a8… ``` Forge registry end to end. The GitHub mirror being blocked lags the public repo and does not touch the deploy.
chore(release): v0.2.15
All checks were successful
CI / cargo (pull_request) Successful in 1m4s
Details
CI / tag-ancestry (pull_request) Successful in 4s
Details
CI / docker (pull_request) Successful in 2m19s
Details
ad94486a6d
 
Carries the ancestry gate on tag builds, the X-Forwarded-For entry-count
measurement, and the AGENTS.md corrections from 2026-08-26/27.

Also records the second route to a local green on the wrong compiler: with
RUSTUP_TOOLCHAIN unset, mise's rustc shim resolves stable (1.98.0) and ignores
rust-toolchain.toml's 1.93.0. clippy::naive_bytecount fires on 1.93.0 and the
shim would have passed it to CI.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jlxq0 merged commit 3d919ef4f3 into main 2026-08-27 03:17:34 +00:00
jlxq0 deleted branch release/v0.2.15 2026-08-27 03:17:34 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
waiting-on-julian
Blocked on Julian. The ask is in the issue.

No labels
waiting-on-julian
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jlxq0/jmap-mcp!19
No description provided.