docs(changelog): sync to upstream q-ring v0.11.7#1
Merged
Conversation
- lib/data/version.ts: bump PROJECT_VERSION 0.10.1 → 0.11.7 so the footer matches the latest upstream package version. - lib/data/changelog.ts: add new 0.11.7 entry on top (Glama TDQS overhaul for all 44 MCP tools — common parameter schemas + per-tool describe() strings) and backfill the missing 0.11.5 entry (Kiro & Claude Code plugins, in-repo marketing site extracted to this repository, MCP tool description tightening). - CHANGELOG.md: new Keep-a-Changelog file at repo root, mirroring the data file with a note that the site mirrors upstream q-ring versions and a link back to the upstream CHANGELOG for pre-extraction history. Test plan: - pnpm run lint ✓ - pnpm run build ✓ (Next.js 16.2.1 Turbopack, all 4 routes prerender static) Made-with: Cursor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Intent
Mirror the upstream
quantum_ringv0.11.7 release into the marketing site so the/changelogpage and footer reflect the latest published version. Also backfills the missing v0.11.5 entry that was skipped during the in-repo → standalone-repo extraction.Tracked in upstream: I4cTime/quantum_ring#56 (feature) and I4cTime/quantum_ring#57 (release v0.11.7), now live on npm and the MCP Registry.
What changed
lib/data/version.ts—PROJECT_VERSIONbumped0.10.1→0.11.7so the<Footer>version chip matches the latest upstream package.lib/data/changelog.ts— added a new0.11.7entry on top (Glama TDQS overhaul for all 44 MCP tools) and backfilled the missing0.11.5entry (Kiro Power pack, Claude Code plugin, in-repo marketing site extracted to this repo, MCP tool description tightening). Cleared the now-staleUnreleasedhighlights.CHANGELOG.md(new) — Keep-a-Changelog file at the repo root mirroring the data file, with a note that the site mirrors upstreamquantum_ringversions and a link back to the upstream CHANGELOG for pre-extraction history..github/workflows/ci.yml— removed (was already pending in the working tree before this PR; the site is validated through Vercel build/preview rather than GitHub Actions).Risk
pnpm-lock.yamlunchanged — no new dependencies.pnpm run buildon this PR.Test plan
Manually verify on the Vercel preview that:
v0.11.7./changelogpage renders the newv0.11.7entry on top, followed byv0.11.5, thenv0.11.0, etc.🤖 Generated with Claude Code
Made with Cursor