Skip to content

chore(release): bump runtime version 0.1.4 -> 0.1.5#154

Merged
vigneshsubbiah16 merged 1 commit into
stagingfrom
chore/bump-0.1.5
Jun 15, 2026
Merged

chore(release): bump runtime version 0.1.4 -> 0.1.5#154
vigneshsubbiah16 merged 1 commit into
stagingfrom
chore/bump-0.1.5

Conversation

@vigneshsubbiah16

@vigneshsubbiah16 vigneshsubbiah16 commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

What

Bumps both binaries' __version__ from 0.1.4 to 0.1.5, in lockstep:

  • binary/src/unbound_hook/__init__.py
  • packaging/unbound_discovery_entry.py

Why

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 the runtime-v0.1.5 release that carries the stdout-encoding crash fix (#153) to the fleet.

No behavior change — version strings only. Per the in-file WEB-4802 note, 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.5

Greptile Summary

Bumps __version__ from 0.1.4 to 0.1.5 in both unbound_hook and unbound_discovery_entry in 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 the WEB-4802 TODO 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

Filename Overview
binary/src/unbound_hook/init.py Single-line version bump from "0.1.4" to "0.1.5"; no logic changes.
packaging/unbound_discovery_entry.py Single-line version bump from "0.1.4" to "0.1.5" to match the hook version per the WEB-4802 lockstep requirement; no logic changes.

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)"]
Loading

Reviews (1): Last reviewed commit: "chore(release): bump runtime version 0.1..." | Re-trigger Greptile

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 vigneshsubbiah16 requested a review from a team June 15, 2026 18:04
@vigneshsubbiah16 vigneshsubbiah16 merged commit c45c45a into staging Jun 15, 2026
2 checks passed
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>
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