Skip to content

DEV-2100: namespace docs-example buckets#59

Merged
demtario merged 1 commit into
feature/DEV-2099_Versioned-docs-examplesfrom
feature/DEV-2100_bucket-foundation
Jul 17, 2026
Merged

DEV-2100: namespace docs-example buckets#59
demtario merged 1 commit into
feature/DEV-2099_Versioned-docs-examplesfrom
feature/DEV-2100_bucket-foundation

Conversation

@demtario

@demtario demtario commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Task: https://app.clickup.com/t/9015210959/DEV-2100

  • require a docs branch and write each import to its version-specific bucket
  • resolve develop from npm dist-tags.next and make registry/version failures fatal
  • add bucket-resolution and fixture tests, including sibling-bucket preservation

Test plan

  • pnpm test
  • pnpm typecheck in packages/runtime
  • pnpm typecheck in apps/authoring

Deferred

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.mjs now requires --docs-branch: prod-docs/<major.minor> writes under <bucket>/ (e.g. 18.0) and develop writes the next bucket. 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 sibling handsontable/package.json semver; develop uses npm dist-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 resolveDocsBucket in @handsontable/demo-runtime to map a selected HOT version to a bucket (exact match for next, major.minor for releases, no silent fallback to next). Docs and pnpm 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.

@demtario
demtario marked this pull request as ready for review July 17, 2026 10:14
@demtario demtario self-assigned this Jul 17, 2026
@demtario
demtario requested a review from budnix July 17, 2026 10:16
@demtario
demtario merged commit f5ebd88 into feature/DEV-2099_Versioned-docs-examples Jul 17, 2026
2 checks passed
@demtario
demtario deleted the feature/DEV-2100_bucket-foundation branch July 17, 2026 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants