Declare the versioned surface, drop Docker, and cut 1.9.7 - #22
Open
anderslindho wants to merge 3 commits into
Open
Declare the versioned surface, drop Docker, and cut 1.9.7#22anderslindho wants to merge 3 commits into
anderslindho wants to merge 3 commits into
Conversation
recsync's integration tests pull ghcr.io/channelfinder/reccaster:master, which is republished on every push to the default branch. Republishing that tag on 2026-08-03 carried the /recsync to /reccaster path rename from 7d12820 and stopped recsync's integration IOC from initialising. Nothing on their side had changed. Discussion on #21 agreed the image does not belong in an EPICS module repository, and that moving the build to recceiver or recsync would recreate the coupling recsync#158 is trying to end.
`5ff76af` adopted Semantic Versioning by linking the spec, but never said what the public interface is, which clause 1 asks for. Without that, it was unclear whether the container image counted, and the path rename inside it did not look like a breaking change to anyone consuming the image. #21 settled that the image is outside the surface. Record the module boundary here so later releases have a rule to apply.
Nothing has been tagged since the split, so the [Unreleased] section has been accumulating without a release to attach it to. Nothing in the versioned surface changed this cycle: no change to `db/` or `reccaster.dbd`, no iocsh function, no soname bump. Cut it as 1.9.7.
anderslindho
requested review from
jacomago,
mdavidsaver,
ralphlange,
shroffk,
simon-ess and
tynanford
August 14, 2026 09:39
This was referenced Aug 14, 2026
|
jacomago
approved these changes
Aug 14, 2026
tynanford
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
recsync's integration tests pull
ghcr.io/channelfinder/reccaster:master, which is republished on every push to the default branch. Republishing that tag on 2026-08-03 carried the/recsyncto/reccasterpath rename from7d12820, which stopped recsync's integration IOC from initialising. Nothing on their side had changed.Discussion on #21 settled that the container image is not part of the versioned surface, and that it does not belong in an EPICS module repository. Moving the build to recceiver or recsync would recreate the coupling recsync#158 is trying to end, so this removes
Dockerfile,.dockerignore, and.github/workflows/docker.ymlinstead. Sites building the module from source are unaffected; downstream consumers of the image will need to decouple on their side.5ff76afadopted Semantic Versioning by linking the spec, but never said what the public interface is, which clause 1 asks for. This records the module boundary inCHANGELOG.md: the databases indb/,reccaster.dbd, the iocsh functions the module registers, the library soname, and any headers it installs. The wire protocol is left out: it is shared with other implementations, and this repository cannot version it alone.This also cuts the accumulated
[Unreleased]entries as 1.9.7 and adds the compare links. Nothing in the versioned surface changed this cycle, so the release is a patch rather than a minor or major bump.recsync#173 asked for a versioned image to pin; once this lands that path is gone and the remaining work is decoupling on the recsync side (recsync#158).