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
{{ message }}
Repository navigation
Commit 738ff33
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CHANGELOG.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,21 @@ The format follows [Keep a Changelog](https://keepachangelog.com); releases are
19
19
Consumers must read `CARGO_TARGET_DIR` rather than assume `./target`.
20
20
-`docs/self-hosted.md`: how a host hands these variables to every job through the runner's job-started hook, which reaches `container:` jobs too.
21
21
22
+
### Changed
23
+
24
+
-`cargo-docker`: `--offline` goes in front of the cargo subcommand, so `args` may end in `-- <arguments for the test binary>`.
25
+
-`_lib/seal.sh`: `target-dir` and `cargo-cache` accept absolute paths, which lets a sealed action reuse rust-cache's `local-target` directory.
26
+
-`publish-dry-run`: the prep refuses a `.crate` whose file list contains a cargo build tree or a cargo home, instead of validating an archive that packages them.
27
+
-`changelog`: candidate marker tags (`vX.Y.Z-rcN`) no longer set the baseline for a stable version; a release-candidate version still measures against earlier candidates.
28
+
-`cargo-publish` and every snippet: `rust-lang/crates-io-auth-action` sets a `token` output, which is passed as `registry-token`; it never exported `CARGO_REGISTRY_TOKEN`.
29
+
30
+
### Fixed
31
+
32
+
-`build-image`: the Actions runtime token is masked before it is exported into the job environment.
33
+
-`publish-draft-release`, `promote-release`: the moving major is force-pushed in one step; the delete that preceded it left `@v1` unresolvable for a moment.
34
+
-`release-guidance`: a release-candidate version keeps its pre-release flag in the rendered publish command.
35
+
-`timing-start`: the sampler exits when its pid file disappears or after six hours, so a cancelled job leaves no loop behind.
0 commit comments