Repository navigation
chore(release): prepare v0.1.0-alpha.3 - #88
Merged
Merged
Conversation
Moves the Unreleased changelog under 0.1.0-alpha.3 with a summary, what did not run for this release, and what changes for someone upgrading from alpha.2. Updates the version in the README, the single-VM guide and the website. Sets the chart's appVersion to 0.1.0-alpha.3. It named 0.1.0, an image tag that was never published, so installing the chart from a checkout could not pull its image; the air-gapped and day-2 guides named the same tag and the chart version 0.2.0 (it is 0.3.0). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: Jalil <reachjalil@gmail.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
4 tasks done
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.
What is this about?
Release prep for
v0.1.0-alpha.3.What problem does it solve?
pre-releaseholds 40-odd commits sincev0.1.0-alpha.2: the capacity scheduler andpausingstatus, the admin console, the live Daytona and Freestyle fixes, and this week's ten defect fixes, the adapter scope cut and the CI changes. None of it is in a published release.The chart's
appVersionalso named0.1.0, an image tag that was never published, so installing the chart from a checkout could not pull its image.How is it implemented?
CHANGELOG.md: the Unreleased sections move under0.1.0-alpha.3, with a summary, a plain statement of what did not run for this release, and what changes for someone upgrading from alpha.2 (experimental adapter kinds refused, thepausingstatus,PATCH ttlSeconds: 0is now 400).README.md,docs/deploy/single-vm.md,site/src/pages/index.astro.deploy/helm/differently/Chart.yaml:appVersion: "0.1.0-alpha.3".docs/maintaining.mdadds it to what a release prep PR changes.docs/deploy/air-gapped.md,day-2.md,kubernetes.md: image tag0.1.0and chart version0.2.0corrected.After this merges, the signed tag
v0.1.0-alpha.3goes on the merge commit, as the earlier alphas did.How was it tested?
pre-releasetip this branches from:make verifypasses (default and experimental builds, both SDK suites, Helm lint), and a dev server built from it ran the quickstart, refused a negative TTL and ane2bpool, and listed audit events newest first.make helm-lintpasses and the chart rendersdifferently-server:0.1.0-alpha.3;npm run buildinsite/passes.make test-postgreslocally (the Postgres conformance job ran in CI on each PR). The changelog says so.verifyjob in ci(release): run the checks before a tag publishes anything #87; the tag push is its first run.Checklist
make verifypasses (on the base tip; this PR changes docs and the chart's appVersion)git commit -s)api/openapi.yaml, both SDKs anddocs/feature-parity.md(no API change)🤖 Generated with Claude Code