Prepare release 1.1
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, haskell
- Domain
- build-system, ci-cd, release
Research direction
Read the release checklist in this issue, then inspect MAINTAINERS.md, CHANGELOG.md, MODULE.bazel files, the start script, haskell/private/versions.bzl, and the Prepare Release workflow. Review changes since the previous release and follow the listed checks; done means the release branch and PR are merged, the release is published, and the deployed start script is current.
Written by the indexing model from the issue text.
Description
- Read through this process in its entirety so you understand it.
- Create and checkout a new release preparation branch, named
release-<major>.<minor>. - If the minimal Bazel version has changed:
- update it in the
startscript, inhaskell/private/versions.bzl, in theREADMEand inpresubmit.ymlfiles from the.bcrfolder - add a note about this change to the
CHANGELOG
- update it in the
- Remove any feature that is still too experimental to go into a
release, by cherry-picking reverts (or by manually deleting the
feature).- Check the list here
for PRs that have been explicitly marked for removal, if any.
- Check the list here
- Amend the
CHANGELOGby summarising all significant
pull requests since the last release (see
here). Specifically:- Add a "Highlights" section for major improvements/changes.
- Create "Added", "Removed", "Changed" and "Fixed" sections, as
necessary. - If relevant, add links to the corresponding PRs to the entries.
- Update the version of the modules in
MODULE.bazelfiles - Push the
release-<major>.<minor>branch and open a PR; go through review and merge upon success. - Trigger the
Prepare Releaseworkflow- either via the Github UI or
- run
gh workflow run -f version=<major>.<minor> 'Prepare Release'using the Github CLI
- Go to the releases, open the draft release which was created to inspect it
- Do the code snippets look valid?
- Is there a release artifact attached to it?
- If you're happy, publish the release... 🚀
- After the "Publish" workflow is finished check whether https://haskell.build/start
is now the lateststartscript (Netlify sometimes has problems). - Announce the new version on Twitter by asking someone with access.
- Dominant language
- Starlark
- Stars
- 279
- Forks
- 94
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tweag/rules_haskell
-
cc_wrapper crashes with ValueError on Windows when a path is on another drivePossibly taken @TrapsterDK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
tweag/rules_haskell#2492 ·
Maintainers usually reply within 1 day
-
Track CI failuresOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
tweag/rules_haskell#2456 · 96 comments ·
Maintainers usually reply within 1 day
-
type: feature request
Difficulty 5/5 Over a week Newbie friendliness 25/100
tweag/rules_haskell#2451 ·
Maintainers usually reply within 1 day
-
os:windows type: bug
Difficulty 4/5 3-5 days Newbie friendliness 50/100
tweag/rules_haskell#2447 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
tweag/rules_haskell#2426 · 1 comment ·
Maintainers usually reply within 1 day
All issues in tweag/rules_haskell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Netcracker/qubership-authz-agent#311 ·
Maintainers usually reply within 1 day
-
deploy-image adds Recorder to the wrong reconciler when another controller name ends with the kindOpenrelease-blocker
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
kubernetes-sigs/kubebuilder#6191 ·
Maintainers usually reply within 1 day
-
Pin Python to 3.14 in the era5grib-parallel environment specificationPossibly taken @atteggiani claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ACCESS-NRI/containerised-environments-infra#129 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
briandconnelly/data-reasoning#106 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/skill-recorder#113 · 1 reaction ·
Maintainers usually reply within 1 day