Upgrade GramFrame to v0.1.13#111
Merged
Merged
Conversation
Contributor
|
📄 HTML preview for this PR is live:
Rebuilt on every push to this PR; removed when the PR closes. (May take a minute for GitHub Pages to refresh.) |
Adopt GramFrame v0.1.13. Changes since v0.1.11 are non-breaking for our
integration (no class/attribute API changes):
- v0.1.12: refresh markers/harmonics tables when clearing a gram
(DeepBlueCLtd/GramFrame#180).
- v0.1.13: single version source of truth, version embedded in
demo/preview builds, GramFrame version surfaced as the Pan-button
tooltip (DeepBlueCLtd/GramFrame#181).
This is a pure bundle + VERSION bump — no generator or CSS changes:
- Replace all three gramframe.bundle.js copies (scripts/vendor/gramframe/,
theme/gramframe-oxygen/resources/, presentation/assets/embeds/) with the
v0.1.13 bundle (byte-identical across the three; the in-bundle VERSION
string now reads 0.1.13).
- Bump both VERSION files to v0.1.13.
- Refresh the stale version reference in theme/gramframe-oxygen/README.md
(was v0.1.9) to match resources/VERSION.
Landing this on main retriggers the package-release workflow (theme/**
is a release path), cutting a fresh air-gap deliverable zip.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HXpaibPmL8HyKjHUuRthyi
IanMayo
force-pushed
the
claude/gramframe-release-update-g9849a
branch
from
20ac486 to
9155262
Compare
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
2 participants
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
Adopts GramFrame v0.1.13 across the pipeline. (Supersedes the earlier v0.1.12 bump on this branch — v0.1.12 was never released, so this PR jumps straight to v0.1.13.)
Changes since v0.1.11 are non-breaking for our integration — no class/attribute API changes, so unlike the v0.1.11 bump this needs no generator (
generate_dita.py) or CSS changes:Changes
gramframe.bundle.jscopies with the v0.1.13 bundle, byte-identical across all three (thetest_package_releasesync contract enforces vendor ↔ theme parity):scripts/vendor/gramframe/gramframe.bundle.jstheme/gramframe-oxygen/resources/gramframe.bundle.jspresentation/assets/embeds/gramframe.bundle.jsVERSIONfiles tov0.1.13.theme/gramframe-oxygen/README.md(it still readv0.1.9).Release
Merging to
mainretriggers the Package release workflow (theme/**is a release trigger path), which gates on the test suite and cuts a fresh air-gap deliverable zip +.sha256.Testing
python -m unittest discover tests/→ 304 passed (1 skipped).test_package_releaseconfirms the theme bundle stays byte-identical to the vendored bundle.🤖 Generated with Claude Code