chore(release): 0.7.5 — complete changelog for the SEO/agent-discovery batch (NJS-SEO-3..5) - #34
Merged
Merged
Conversation
The 0.7.5 section now covers everything shipped since v0.7.0, not just the CI toolchain: SEO surfaces (sitemap, robots, OG/canonical, site verification), Jev/Laya guide across AI assets, the 2026-09 benchmark refresh with citable claims, and the example MCP server with contract tests. proof.md release history stays a dated snapshot by design.
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
1 participant
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.
What
Completes the 0.7.5 changelog so the release notes cover everything shipped since v0.7.0, not just the CI toolchain. This is the release PR: merging it lets the Release workflow publish @sebasoft/[email protected] to npm and push tag
v0.7.5.Changelog entries added (0.7.5 section)
What this PR does NOT do (by design)
proof.mdrelease history is a dated snapshot (2026-09-22) of v0.7.0 facts — the file itself says to re-check after a new publish. It stays untouched; a post-publish update comes separately.Version state
package.json= 0.7.5 (bumped in chore(ci): Node 24 standard, actions v7, changesets v2 (NJS-SEO-3) #31)docs/overview.mdalready says `0.7.5` source release`CHANGELOG.mdnow has the full 0.7.5 section (this PR)release-surfaces.test.tsenforces manifest/changelog/overview alignment — passingVerification
yarn docs:build: greenPost-merge
Release workflow runs on push to main. Action needed from you (repo admin): the workflow uses
environment: productionwith required reviewer approval — approve the pending deployment when the run appears, and npm gets 0.7.5 with provenance + tag v0.7.5.Alternative if you want to avoid the gate: merge this PR and I cancel the run as before, keeping the hold; then when you say go, next push publishes. Say the word.