release: 1.17.2 — ship GEO README to npm - #41
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs-only patch release: ship the GEO README to npm
The published npm
@alloevil/agent-xray@1.17.1(2026-09-07) predates the SEO/GEOREADME restructure, which merged in #39 on 2026-09-08. npm only refreshes a
package's README when a new version is published, so npmjs.com / npm.io still
serve the old README (npm.io ranks #3 for a descriptive AgentXRay query — high
value to get the good README there).
No code changes. Only
package.jsonversion1.17.1 → 1.17.2.The README already carries the restructured sections that this release exists to
publish:
## What it is,## When to use it,## When NOT to use it,## Install,## FAQ. The npm README is the repoREADME.mdat pack time(
filesincludesREADME.md; no build step rewrites it).How to publish after merge
A release-triggered publish workflow already automates publishing
(
.github/workflows/publish.yml,on: release: types: [published]→npm ci→ pack → build provenance →
npm publish --provenance --access public). It alsobuilds
frontend/distin CI via thepreparescript, so nothing needs buildinglocally. Creating the GitHub Release both creates the tag and fires the workflow:
Prerequisite: the
NPM_TOKENrepo secret (already referenced by theworkflow). Publishing runs in CI with a token, so there is no interactive 2FA/OTP
prompt. No manual
npm publishis needed.Do not merge yet — publishing is the maintainer's step.