chore(release): bump runtime version 0.1.4 -> 0.1.5#154
Merged
Conversation
Lockstep bump of both binaries' __version__ (unbound-hook + discovery) so the release workflow's publish-safety assert passes when tagging runtime-v0.1.5. This is the release that carries the stdout-encoding fix (#153) to the fleet. No behavior change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
vigneshsubbiah16
added a commit
that referenced
this pull request
Jun 15, 2026
* fix(unbound-hook): never let stdout encoding abort onboarding setup (#153) Jamf's recurring check-in runs the MDM onboarding policy from a launchd context with no LANG/LC_* set, so the interpreter falls back to the ASCII stdout codec. The first diagnostic line setup prints — the migration banner "[migration] python->binary sweep" — contained a U+2192 arrow, which raised UnicodeEncodeError and aborted `setup` (exit 1 -> UNBOUND_INSTALL_FAILED step=setup) on every check-in. Interactive `sudo jamf policy` runs inherit a UTF-8 locale and passed, which masked it during canary. The output is purely diagnostic; a cosmetic write should never kill the install. - main(): reconfigure stdout/stderr to UTF-8 (errors='replace') before dispatching any subcommand, so no print can raise UnicodeEncodeError. Also hardens the `hook` path, whose stdout carries UTF-8 JSON. - setup_cmd: swap the banner arrow for ASCII '->' as defense in depth. - test: drive main(["setup", ...]) with ASCII-backed streams; reproduces the exact crash pre-fix, passes post-fix. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore(release): bump runtime version 0.1.4 -> 0.1.5 (#154) Lockstep bump of both binaries' __version__ (unbound-hook + discovery) so the release workflow's publish-safety assert passes when tagging runtime-v0.1.5. This is the release that carries the stdout-encoding fix (#153) to the fleet. No behavior change. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
What
Bumps both binaries'
__version__from0.1.4to0.1.5, in lockstep:binary/src/unbound_hook/__init__.pypackaging/unbound_discovery_entry.pyWhy
The release workflow (
release-macos-runtime.yml) reads__version__from both files and refuses to publish if they don't match the release tag (bump BOTH __version__ ... to $version). This bump prepares theruntime-v0.1.5release that carries the stdout-encoding crash fix (#153) to the fleet.No behavior change — version strings only. Per the in-file
WEB-4802note, hook and discovery versions must move together until build-time version injection lands.Release path
merge #153 (done) + this bump -> staging -> main -> tag runtime-v0.1.5Greptile Summary
Bumps
__version__from0.1.4to0.1.5in bothunbound_hookandunbound_discovery_entryin lockstep, as required by the release workflow.binary/src/unbound_hook/__init__.py: version string updated to\"0.1.5\".packaging/unbound_discovery_entry.py: version string updated to\"0.1.5\", consistent with theWEB-4802TODO that mandates both values stay equal until build-time version injection lands.Confidence Score: 5/5
Safe to merge — both version strings are updated in lockstep and no executable logic is changed.
Both files change only a single version string constant. The lockstep requirement documented in the WEB-4802 TODO is satisfied: both files now read "0.1.5". No logic, migrations, API contracts, or security-sensitive code is touched.
No files require special attention.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["PR #154: bump __version__ 0.1.4 → 0.1.5"] --> B["binary/src/unbound_hook/__init__.py\n__version__ = '0.1.5'"] A --> C["packaging/unbound_discovery_entry.py\n__version__ = '0.1.5'"] B --> D{Versions match?} C --> D D -- Yes --> E["release-macos-runtime.yml\npasses version check"] D -- No --> F["Workflow refuses to publish"] E --> G["Tag: runtime-v0.1.5\n(carries stdout-encoding fix from #153)"]Reviews (1): Last reviewed commit: "chore(release): bump runtime version 0.1..." | Re-trigger Greptile