Skip to content

release: prepare CraftDAG v0.2.6 - #113

Merged
madawei2699 merged 1 commit into
mainfrom
release/craftdag-0.2.6
Aug 26, 2026
Merged

release: prepare CraftDAG v0.2.6#113
madawei2699 merged 1 commit into
mainfrom
release/craftdag-0.2.6

Conversation

@madawei2699

Copy link
Copy Markdown
Contributor

Summary

  • bump the published CraftDAG packages for the merged curved RectRing cornerRise capability
  • core 0.2.6, exporter-schem 0.2.5, importer-schem 0.2.4
  • keep the unpublished CLI at 0.2.0

Validation

  • pnpm test (core 180, exporter 6, importer 3, CLI 10)
  • pnpm lint
  • pnpm typecheck
  • curved geometry stress coverage passes

The tag-triggered publish workflow should run after this release commit is merged.

@madawei2699
madawei2699 merged commit 5242747 into main Aug 26, 2026
1 check passed
@madawei2699
madawei2699 deleted the release/craftdag-0.2.6 branch August 26, 2026 08:31

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c59ec3ff19

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

{
"name": "@i365dev/craftdag-core",
"version": "0.2.4",
"version": "0.2.6",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Synchronize exported versions with package releases

When consumers inspect these packages for diagnostics or compatibility checks, the newly published core 0.2.6, exporter 0.2.5, and importer 0.2.4 will all still report 0.2.0 through version, exporterVersion, and importerVersion respectively. Update those exported constants (and the core assertion in bootstrap.test.ts) alongside the manifest versions so the public runtime metadata identifies the installed release correctly.

Useful? React with 👍 / 👎.

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.

1 participant