Repository navigation
docs(website): sync published v1.6.0 surfaces - #250
Merged
Merged
Conversation
- Refresh the trusted website release snapshot and changelog state after GitHub Release v1.6.0 became public. - Pin the bilingual CLI package.json and container recipes to 1.6.0 so the release-event website test passes. - Regenerate the Homebrew cask and formula and the local winget manifests from the published SHA256SUMS.txt. - Drop the not-in-public-1.5.1 caveats for capsule verify and verify-suite, which ship in CLI 1.6.0.
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.
Summary
latest-release.json, 20 assets) and changelog state after GitHub Release v1.6.0 became public.package.jsonand container recipes to 1.6.0.SHA256SUMS.txt(generate-distribution-manifests.mjs --tag v1.6.0). Winget is not submitted while Windows remains unsigned.capsule verify/verify-suiteship in CLI 1.6.0 (checked in the publishedlinguacode-cli-1.6.0.tgzhelp output), so the "not in public CLI 1.5.1" caveats in docs and the CLI reference now say "1.6.0 and later".Reproduced defect
The
release: publishedwebsite deploy failed the EN/ES recipe assertionen recipes should pin package.json and container examples to public 1.6.0; build and deploy were skipped, soupdates.linguacode.dev/web/versionstill reports 1.5.1.Validation
npm --prefix website run sync:check,check(55/55 tests,astro check0 errors, release snapshot and CLI reference checks) andbuildpass./releases,/changelog,/cli/recipes,/cli/referencein EN and ES return 200 and show 1.6.0; the only remaining 1.5.1 is the previous changelog entry; zero console errors.pnpm exec vitest run tests/scripts/distributionManifests.test.ts: 24/24.Merge condition
Do not merge until
@linguacode/cli@1.6.0is public on npm. Publish CLI run 38588936348 passed the immutable-artifact verification and is waiting fornpm-productionapproval and npm 2FA staging approval; publishing the website first would advertise a package users cannot install.