You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* docs: bump example actions/checkout to v7; pin example to v0.1.3
The README workflow examples used actions/checkout@v6 (latest is v7)
and an illustrative oasdiff-action pin at v0.1.1 (latest is v0.1.3).
The recommended oasdiff-action pin (@v0 moving tag) is unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* docs: stop hardcoding an exact action version in the Versioning section
The exact-pin example hardcoded a patch version (@v0.1.3) that just goes
stale (it was @v0.1.1 before). Keep @v0 as the concrete recommended
example and point to the Releases page for users who want to pin an
exact tag, so the README has no version number to rot.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* docs: 'examples above' -> 'examples here' in Versioning
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
@@ -55,19 +55,13 @@ This compares your spec on the PR branch against the base branch and fails the w
55
55
56
56
## Versioning
57
57
58
-
The examples above pin the action at `@v0`, the moving major-version tag. It always points at the latest `v0.x.y` release, so you get every later patch and minor (including review and PR-comment improvements) automatically, with no workflow change:
58
+
The examples here pin the action at `@v0`, the moving major-version tag. It always points at the latest `v0.x.y` release, so you get every later patch and minor (including review and PR-comment improvements) automatically, with no workflow change:
59
59
60
60
```yaml
61
61
- uses: oasdiff/oasdiff-action/breaking@v0
62
62
```
63
63
64
-
`@v0` only advances on stable releases, never on prereleases. If you prefer to control upgrades yourself, pin an exact release instead and bump it when you choose:
65
-
66
-
```yaml
67
-
- uses: oasdiff/oasdiff-action/breaking@v0.1.1
68
-
```
69
-
70
-
`@main`runs the unreleased tip and is meant for trying changes early, not for production.
64
+
`@v0`only advances on stable releases, never on prereleases. If you prefer to control upgrades yourself, pin to a specific release tag from the [Releases page](https://github.com/oasdiff/oasdiff-action/releases) and bump it when you choose. `@main` runs the unreleased tip and is meant for trying changes early, not for production.
0 commit comments