Release v0.2.0 - #44
Merged
Merged
Conversation
Changelog only. The package manifests stay at 0.0.0 deliberately: the facade pins "@idfkit/core": "0.0.0", and that exact string is what makes npm resolve the workspace link locally instead of reaching for the registry. publish.yml rewrites both the versions and the facade's dependency specs from the tag in its own checkout, which is where those numbers belong. Promotes [Unreleased] to [0.2.0]. Also corrects two things the section had wrong: it named governance-2026.11 when the level is now 2026.12, and it did not mention SchemaBundle.loadProse and prose() at all. The preamble's lockstep list gained @idfkit/language, which joins it in this release.
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
1 participant
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.
Changelog only. Promotes
[Unreleased]to[0.2.0], dated 2026-09-04.The package manifests stay at
0.0.0, deliberately. The facade pins"@idfkit/core": "0.0.0", and that exact string is what makes npm resolve the workspace link locally instead of reaching for the registry.publish.ymlrewrites both the versions and the facade's dependency specs from the tag in its own checkout, which is where those numbers belong. Same as therc.2release commit.Two things the section had wrong
governance-2026.11when the level is now2026.12. Rewritten to say what each level carries.SchemaBundle.loadProse()andprose()at all, which shipped in Let a consumer of the shared name reach the schema prose #41. Added underAdded.The preamble's lockstep list gained
@idfkit/language, which joins it in this release.Audit
Three commits since
v0.2.0-rc.2: #40 and #41 are covered; #42 is release tooling with no user-visible effect and stays out. ISO dates, reverse-chronological order, no empty categories, compare links regenerated.One thing flagged and not changed:
[0.2.0-rc.1]carries a### Migrationsection, outside the six Keep a Changelog categories. It holds the rename table and sits in a released section, so re-bucketing it would either bury the table or move an anchor people may have linked.What happens after this merges
gh release create v0.2.0firespublish.yml, which publishes six packages to npm under thelatestdist-tag, including the first real versions of@idfkit/language,@idfkit/types-v26-1and@idfkit/types-v9-4in place of their0.0.0bootstrap stubs. The facadeidfkitis not published:publish_facadedefaults to false.