Skip to content

chore(deps): update golang.org/x/exp digest to 746e56f#973

Merged
cpcloud merged 2 commits intomainfrom
renovate/go-indirect
Apr 23, 2026
Merged

chore(deps): update golang.org/x/exp digest to 746e56f#973
cpcloud merged 2 commits intomainfrom
renovate/go-indirect

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 23, 2026

This PR contains the following updates:

Package Type Update Change
golang.org/x/exp indirect digest 3dfff04746e56f

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 23, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@cpcloud cpcloud merged commit ec1c910 into main Apr 23, 2026
30 checks passed
@cpcloud cpcloud deleted the renovate/go-indirect branch April 23, 2026 11:11
cpcloud added a commit that referenced this pull request Apr 23, 2026
Two fixes tied to PR #974, where `update-vendor-hash.yml` committed
`sha256-AAAAAAAAAAAA...=` to `nix/package.nix`.

## What went wrong

Renovate opened #974 to major-bump `github.com/openai/openai-go`
(indirect). Nothing in the repo imports `openai-go/v3` — `go mod why
github.com/openai/openai-go/v3` reports `(main module does not need
package ...)` — so `go mod tidy` in the vendor-hash workflow removes it.
The vendor contents then match the pre-PR state, so `new_hash ==
old_hash`.

The compute step writes the fake sentinel first, runs `nix build`,
parses `got: sha256-...`, then — on the `old_hash == new_hash` branch —
exits before the final `sed` that restores the real hash. `go mod tidy`
still left `go.mod`/`go.sum` changes, so `git diff --cached` wasn't
empty, and `Commit and push` ran with the fake hash still in
`nix/package.nix`. `Verify build` was gated on `changed == 'true'` so it
was skipped. See run
[24829437487](https://github.com/micasa-dev/micasa/actions/runs/24829437487):
`vendorHash unchanged
(sha256-wDz1EKWKPkubV8NcBGQnLnRi4XT0rCjOQBKtO/yRdds=), nothing to do`
immediately followed by `[renovate/major-go-indirect ee7cceb] chore:
update vendorHash for Go dependency changes`.

## Changes

- `.github/workflows/update-vendor-hash.yml` — move the restoration
`sed` ahead of the unchanged-check, so the file always holds a real hash
before any exit. Pipe `grep` through `head -n1` as a defense against
multi-line output.
- `renovate.json` — set `separateMajorMinor`, `separateMultipleMajor`,
and `separateMinorPatch` to `false` on the `go-indirect` rule so every
indirect update lands in one PR regardless of semver level.

## Reproduction

1. Open a Renovate PR that bumps only an unused indirect dep (e.g.
`openai-go` v1 → v3).
2. `update-vendor-hash.yml` fires on the push.
3. `go mod tidy` removes the unused dep; vendor contents unchanged.
4. Before the fix: fake hash is committed. After the fix: the real hash
is restored and only `go.mod`/`go.sum` (if tidied) end up in the commit.

## Follow-up

PR #974 still has the fake-hash commit in its branch history and now
conflicts on `nix/package.nix` with #973's legitimate vendorHash update.
Once this merges, close #974 — Renovate will open a replacement under
the new batched config.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant