Skip to content

Upgrade Executor to v1.6.10 - #4

Merged
willtcarey merged 1 commit into
mainfrom
upgrade-executor-1.6.10
Oct 8, 2026
Merged

willtcarey merged 1 commit into
mainfrom
upgrade-executor-1.6.10

Conversation

@willtcarey

Copy link
Copy Markdown
Member

Bumps the upstream Executor version from v1.6.8 to v1.6.10.

Why

Everhour refuses Executor's token refreshes with invalid_scope, because v1.6.8 re-sends the recorded scope on every refresh. Each Everhour connection stops working once its first access token expires. v1.6.10 includes UsefulSoftwareCo/executor#1982, which retries the refresh once without scope when it's refused that way.

Changes

  • EXECUTOR_VERSION is now v1.6.10.
  • Bun is pinned to 1.3.11 by digest, and the build stage installs python3, make and g++, matching upstream's self-host Dockerfile in this release.
  • The README's release example uses v1.6.10-bnb.1.

Upstream's runtime image now runs as UID 65532. That isn't adopted here: our /data volume was written by the root-running image, and switching would need its ownership changed first.

Testing

Built the runtime target locally and ran it with an empty data directory. It started with the 1Password plugin loaded, and /api/health and /api/setup-status returned 200.

After merging

Tag v1.6.10-bnb.1 to deploy, then reconnect Everhour once. The current connection's refresh has already been refused.

v1.6.10 retries an OAuth refresh without `scope` when the authorization
server answers invalid_scope (UsefulSoftwareCo/executor#1982). Everhour
refuses our v1.6.8 refreshes that way, so every Everhour connection stops
working once its first access token expires.

Matches upstream's self-host build: Bun is pinned to 1.3.11 and the build
stage gets python3, make and g++. Upstream's runtime image now also runs as
UID 65532; that isn't adopted here because our existing /data volume is
owned by root.
@willtcarey
willtcarey merged commit 2282028 into main Oct 8, 2026
@willtcarey
willtcarey deleted the upgrade-executor-1.6.10 branch October 8, 2026 19:23
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