chore(release): 0.1.0, the release candidates' libraries under a final number - #97
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ibraries' paths Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
This sets the first final release:
smart-data-engine-sdk0.1.0 and@smart-data-engines/sde0.1.0. Merging releases nothing. The owner approved the release, and it happens by tagging this
PR's squash commit and approving the two deployments.
The libraries are the release candidates, unchanged.
git diffbetweenpython-v0.1.0rc1/typescript-v0.1.0-rc.1andmainis empty forpython/src,typescript/src,typescript/binand
typescript/package.json; this PR changes only the version in them. The candidates were verified from the registries on 27 September:npm audit signaturesverifies the npm package on Node 18 and 26;That was the condition
docs/publishing.md§5.5 set for this number.What changed
python/src/sde/__init__.py(0.1.0), andtypescript/package.jsonwith its lockfile(
0.1.0).CHANGELOG.mdhas a0.1.0section: which paths did not change since the candidates, how thecandidates were verified, and what changed around the libraries (fix(release): the npm registry check outlasts the registry's cache; npm trust needs --allow-publish and real 2FA #95, fix(release): the npm job says what it presented and why the registry refused; the documents describe the first release #96).
docs/weather-starter.md: the artefact names a build of this tree produces. The pinned registrycommands stay on the candidates until
0.1.0is on the registries, and change with the otherregistry-state documents afterwards.
What the tags will do
tools/release_tag.pyacceptsrefs/tags/python-v0.1.0andrefs/tags/typescript-v0.1.0on thistree.
tools/npm_dist_tag.py 0.1.0 '["0.1.0-dev.0","0.1.0-rc.1"]'answerslatest: a final version.Later candidates will get
next.0.1.0is a final release. An unpinnedpip installthen prefers it over0.1.0rc1.Tests
make checkwith both live engines, on21c7a9a(the bump):generation-migration.live.test.tsexceeded vitest's default 5 stimeout at a load average of 8 on four threads, from another session's test battery. That is the
fourth live test to do so on this machine today; nothing here touches TypeScript's code.
On the head
e773b84, which changes one changelog sentence:make checkpassed 999 of 999, at a load average of 8.6.The live tests' 5 s budget is fixed separately.
🤖 Generated with Claude Code