Skip to content

Point source-repository head at main - #267

Draft
alunduil wants to merge 1 commit into
mainfrom
alunduil/worktree/charming-warthog
Draft

Point source-repository head at main#267
alunduil wants to merge 1 commit into
mainfrom
alunduil/worktree/charming-warthog

Conversation

@alunduil

Copy link
Copy Markdown
Owner

Summary

One line: source-repository head in collection-json.cabal named develop,
which #82 renamed to main and retired. Now names main.

Closes #266.

Gotchas

The reason this is worth a PR of its own rather than a drive-by in the release
commit: the stanza is not inert metadata. It ships in the sdist, renders on the
Hackage page, and is what cabal get -s clones. Against the currently published
version it fails outright:

$ cabal get -s collection-json-1.3.1.3
Cloning into 'collection-json'...
fatal: Remote branch develop not found in upstream origin
Failed to fetch the source repository for package collection-json-1.3.1.3,
repository location https://github.com/alunduil/collection-json.hs
(git failed with ExitFailure 128).

The published 1.3.1.3 cabal file carries the same branch: develop, so this
broke when the branch was renamed rather than at any upload — it is live on
Hackage today, not a prospective problem.

Sequenced ahead of the 1.3.2.0 tag (#84) so that release is the upload that
fixes the pointer instead of the second one shipping it broken.

Verification

  • cabal check — no errors or warnings.
  • git ls-remote --heads https://github.com/alunduil/collection-json.hs main
    resolves, so the branch the stanza now names exists.
  • Built the sdist and confirmed the extracted collection-json.cabal carries
    branch: main — the fix reaches the artifact, not just the working tree.
  • pre-commit run --files collection-json.cabal passes.

cabal get -s itself can only be exercised post-publish, so the ls-remote and
sdist checks stand in for it until 1.3.2.0 is up.

🤖 Generated with Claude Code

https://claude.ai/code/session_013U3Mvn9yPinG1dRj8p5DEv

The stanza still named develop, which #82 renamed to main and retired.
The value is not inert: it ships in the sdist, renders on the Hackage
page, and drives cabal get -s, which fails today against the published
1.3.1.3 with "fatal: Remote branch develop not found in upstream
origin".

Landing this before the 1.3.2.0 tag makes that release the upload that
fixes the pointer rather than the second one carrying it broken.

Closes #266

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013U3Mvn9yPinG1dRj8p5DEv
@codecov

codecov Bot commented Aug 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.46%. Comparing base (b82a39c) to head (26dbc81).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #267   +/-   ##
=======================================
  Coverage   77.46%   77.46%           
=======================================
  Files           1        1           
  Lines         142      142           
  Branches       27       27           
=======================================
  Hits          110      110           
  Misses          5        5           
  Partials       27       27           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

source-repository head points at the main branch

1 participant