Skip to content

chore: merge master, release 0.43.8-dc.2, document releasing - #9

Merged
alexsavio merged 5 commits into
devfrom
chore/merge-master-bump-0.43.8-dc.2
Aug 10, 2026
Merged

alexsavio merged 5 commits into
devfrom
chore/merge-master-bump-0.43.8-dc.2

Conversation

@alexsavio

@alexsavio alexsavio commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Merges master into dev to pick up feat: write runtime crash output to a file in daemon mode #7, which was merged into master rather than dev and so was absent from the release line. A release cut before this would have silently shipped without the daemon crash-log feature. Clean merge: feat: write runtime crash output to a file in daemon mode #7 only touches main.go, main_nowindows.go, main_windows.go.
  • Bumps GEESEFS_VERSION to 0.43.8-dc.2.
  • Documents the branch model, release commands, and the compute-amis pin in CLAUDE.md, and removes the release workflow's version default. That default duplicated GEESEFS_VERSION and had drifted to 0.43.0-dc.1, so a UI dispatch would have tagged a release nine patches stale. The input is already required, so dispatch prompts for it.

Verified on the merged tree: go build ./... and go vet clean, 62 symlinks unit tests pass, zizmor reports no findings.

Worth deciding separately: master is now upstream 0.43.8 plus one dectris commit, so it is no longer the clean upstream mirror it was after the rebase. Either fork work lands on dev only, or the mirror role moves elsewhere.

alexsavio and others added 4 commits August 10, 2026 12:59
After a successful daemon-mode mount the process closes stdout/stderr,
so Go runtime panics and fatal errors vanish without a trace; syslog
only carries logger output. Arm debug.SetCrashOutput with an append-only
file (default /var/log/geesefs-crash.log, GEESEFS_CRASH_LOG to override)
before closing stderr, with a pid/bucket/mountpoint header line so a
following dump can be attributed to its mount.
Picks up the daemon-mode crash-log feature from #7, which was merged into
master rather than dev, so it was absent from the release line. Merges
master into dev the same way #5 did, then bumps the version.

Also refreshes the release workflow's dispatch default, which otherwise
still offers the previous version.
The release version is a dispatch parameter, so editing the workflow to
change it is unnecessary churn. That is also how the default drifted: it
sat at 0.43.0-dc.1 while the shipped constant had moved on.

Removes the default outright rather than bumping it. It duplicated
GEESEFS_VERSION and went stale the moment that constant moved; the input
is already required, so dispatch prompts for it.

Documents in CLAUDE.md the branch model (dev is the release line, master
mirrors upstream, fork work on master is missing from releases), the
release commands, and the compute-amis pin that a new release has to
follow.
@alexsavio alexsavio changed the title chore: merge master and bump to 0.43.8-dc.2 chore: merge master, release 0.43.8-dc.2, document releasing Aug 10, 2026
Makes dev the documented trunk for all dectris development, and master a
read-only mirror that must always sit on the exact upstream commit the
fork is based on, with the command to verify that invariant.

Spells out the failure mode behind #7: a PR against master leaves its
content absent from dev, and a release cut afterwards ships without it
while nothing fails. Records the recovery, and notes that the pre-rebase
branches still on the remote are superseded.
@alexsavio
alexsavio merged commit a6b351c into dev Aug 10, 2026
2 checks passed
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