letsencrypt / letsencrypt/boulder
go1.27: remove build constraints
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
In #8803 we moved some functions out into build-constrained files in order to use the crypto/mldsa package ahead of Go 1.27's release. Once that's released, bump our go.mod to 1.27 and move those functions back to where they were.
Contributor 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.
Research direction
Start with issue #8803 and inspect the build-constrained files and the functions moved there for the temporary crypto/mldsa compatibility. After Go 1.27 is available, update go.mod to 1.27, move those functions back to their original locations, and run the relevant Go tests to confirm the build remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100