linear-sdk-cli 0.2.1 → 0.2.3
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
CHANGED
|
@@ -4,6 +4,18 @@ All notable changes to this project are documented here. The format is based on
|
|
|
4
4
|
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to
|
|
5
5
|
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
6
6
|
|
|
7
|
+
## [0.2.3](https://github.com/zhendalf/linear-sdk-cli/compare/v0.2.2...v0.2.3) (2026-08-24)
|
|
8
|
+
|
|
9
|
+
### Bug Fixes
|
|
10
|
+
|
|
11
|
+
- **ci:** guard absent release PR output ([#21](https://github.com/zhendalf/linear-sdk-cli/issues/21)) ([ed082bf](https://github.com/zhendalf/linear-sdk-cli/commit/ed082bfc6673736a9705198f8e2a17c9d7b4698d))
|
|
12
|
+
|
|
13
|
+
## [0.2.2](https://github.com/zhendalf/linear-sdk-cli/compare/v0.2.1...v0.2.2) (2026-08-24)
|
|
14
|
+
|
|
15
|
+
### Bug Fixes
|
|
16
|
+
|
|
17
|
+
- **ci:** format and verify release PR heads ([#19](https://github.com/zhendalf/linear-sdk-cli/issues/19)) ([a16244d](https://github.com/zhendalf/linear-sdk-cli/commit/a16244d3355a86d3bdaf290d9ee077b06598125e))
|
|
18
|
+
|
|
7
19
|
## [0.2.1](https://github.com/zhendalf/linear-sdk-cli/compare/v0.2.0...v0.2.1) (2026-08-24)
|
|
8
20
|
|
|
9
21
|
### Bug Fixes
|
package/package.json
CHANGED
|
@@ -77,6 +77,10 @@ In scheduled autonomous mode, merge it only when all of the following are true:
|
|
|
77
77
|
trigger them, while the exact release commit has already passed `main` CI);
|
|
78
78
|
- it is cleanly mergeable with no conflicts, review blockers, or unresolved comments.
|
|
79
79
|
|
|
80
|
+
Release Please may rewrite its PR whenever `main` changes. Record the `headRefOid` used by CI
|
|
81
|
+
and review, then fetch the PR again immediately before merging. If its head changed, discard the
|
|
82
|
+
earlier evidence and repeat diff review, verification, and review-comment checks on the new head.
|
|
83
|
+
|
|
80
84
|
After an approved merge, confirm the release workflow completed, then verify the GitHub Release,
|
|
81
85
|
the npm package version, and the `latest` dist-tag. npm publishing must retain OIDC provenance.
|
|
82
86
|
Never retry a failed publish by adding an npm token or disabling provenance; report the failure.
|