DEV-2100: namespace docs-example buckets#59
Merged
demtario merged 1 commit intoJul 17, 2026
Merged
Conversation
budnix
approved these changes
Jul 17, 2026
demtario
merged commit Jul 17, 2026
f5ebd88
into
feature/DEV-2099_Versioned-docs-examples
2 checks passed
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
Task: https://app.clickup.com/t/9015210959/DEV-2100
developfrom npmdist-tags.nextand make registry/version failures fatalTest plan
pnpm testpnpm typecheckinpackages/runtimepnpm typecheckinapps/authoringDeferred
Generated docs-example artifacts remain unchanged. Regenerate and remove the legacy flat snapshot only after the bucket-aware client changes land in the feature branch.
PR intentionally merged into another feature branch, to not break production logic with partial changes.
Note
Medium Risk
Changes the docs import contract and on-disk layout (client bucket wiring is deferred), and develop imports now depend on live npm registry data with strict failure modes.
Overview
Docs-example imports are version-bucketed instead of a single flat
docs-examples/tree.import-docs.mjsnow requires--docs-branch:prod-docs/<major.minor>writes under<bucket>/(e.g.18.0) anddevelopwrites thenextbucket. Regenerating one bucket replaces only that directory so sibling snapshots stay intact.Handsontable version baking is centralized in
docs-import-config.mjs: release branches use the siblinghandsontable/package.jsonsemver;developuses npmdist-tags.next, with invalid or missing registry data treated as fatal import errors. Manifests and example entries record bucket, docs branch, and hotVersion.The authoring app gets
resolveDocsBucketin@handsontable/demo-runtimeto map a selected HOT version to a bucket (exact match fornext, major.minor for releases, no silent fallback tonext). Docs andpnpm test(runtime build before pipeline tests) are updated; pipeline and integration tests cover branch rules, version resolution, bucket preservation, and bucket resolution.Reviewed by Cursor Bugbot for commit 21d243c. Bugbot is set up for automated code reviews on this repo. Configure here.