@buildbase/sdk 0.0.62 → 0.0.65
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [0.0.65] - 2026-09-18
|
|
11
|
+
|
|
12
|
+
No change to the package itself: 0.0.65 is 0.0.62's code, released through the corrected pipeline. `v0.0.63` and `v0.0.64` were tagged without a version bump and stopped by the release preflight before anything was published, so neither exists on npm.
|
|
13
|
+
|
|
14
|
+
### Changed
|
|
15
|
+
|
|
16
|
+
- **Releasing works from either direction.** Creating a release in GitHub's UI creates the tag and starts the workflow; its last step used to create the same release again and fail with "a release with the same tag name already exists" - after npm had already published. It now updates the existing release with these notes and the build, and still creates the release when a tag is pushed from the command line.
|
|
17
|
+
- **A GitHub release is only created once npm has the version.** The release job waits for the npm publish.
|
|
18
|
+
- **Everything that can stop a release is checked before anything is published**: the tag against `package.json`, a CHANGELOG section for the version, that the version is not already on npm, and that npm accepts the publish token.
|
|
19
|
+
|
|
10
20
|
## [0.0.62] - 2026-09-18
|
|
11
21
|
|
|
12
22
|
The first published release with tracking. `0.0.61` was tagged but never reached npm (the publish token had expired), so everything below is new relative to `0.0.60`.
|