Skip to content

chore: bump to 0.3.10-alpha.9 for the gosec hardening - #44

Merged
lr00rl merged 1 commit into
integrationfrom
feature/20261024_release-0.3.10-alpha.9
Oct 24, 2026
Merged

lr00rl merged 1 commit into
integrationfrom
feature/20261024_release-0.3.10-alpha.9

Conversation

@lr00rl

@lr00rl lr00rl commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Summary

Version bump and CHANGELOG for v0.3.10-alpha.9: the node-side log path allowlist with its default denylist, the checkpoint and terminal shell fixes (#43), the installer token and mirror work since alpha.7 (#39, #40), and Go 1.26.10 (#41, #42).

v0.3.10-alpha.8 was tagged on e5f769f before a hold reached the release script; its release run was cancelled before publishing. The tag stays where it is and the version is not reused.

No compatibility floor moves. A server whose LATTICE_LOG_PATH_ALLOW reached beyond /var/log/ needs the same entry on each node; the CHANGELOG says so.

Test plan

  • gofmt clean.
  • CI (go test -race -cover ./..., gosec guard, release workflow check).
  • After the tag: release is prerelease and not Latest, -version prints 0.3.10-alpha.9, -compat-json floors unchanged, binaries built with go1.26.10.

The release carries the node-side log path allowlist, the checkpoint and
terminal shell fixes, the installer token and mirror work since alpha.7,
and Go 1.26.10. v0.3.10-alpha.8 was tagged on e5f769f but never
released, so this release skips that version rather than move the tag.
No compatibility floor moves.
@lr00rl
lr00rl merged commit 5158cb8 into integration Oct 24, 2026
1 check passed
@lr00rl
lr00rl deleted the feature/20261024_release-0.3.10-alpha.9 branch October 24, 2026 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant