Add new version line: node 26.8.2
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- nodejs
- Domain
- build-system
Research direction
The payload names the dependency-builds pipeline but no file, so search the repository for existing node source entries and their version refs to find where the new entry belongs. Copy the format of the nearest existing entry and add the 26.8.2 ref, URL and sha256 from the issue. Done when the pipeline config lists 26.8.2 alongside the other Node version lines.
Written by the indexing model from the issue text.
Description
Please edit the dependency-builds pipeline to add the new version line to the relevant dependency/buildpack.
For nginx/nginx-static: Also remove older mainline/stable version.
E.g. If you are adding nginx 1.22, you will remove 1.20. If you are adding 1.23, you will remove 1.21
{source:{type:node,name:node},version:{ref:26.8.2,url:https://nodejs.org/dist/v26.8.2/node-v26.8.2.tar.gz,sha256:67d1e64b1c80faa8be9ee80e78b89c9aa47ddd29a62200a6b053e80b9c8d4245}}
- Dominant language
- Shell
- Stars
- 1
- Forks
- 2
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 cloudfoundry/buildpacks-github-config
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
All issues in cloudfoundry/buildpacks-github-config
Similar issues
-
verify: just verify runs tools/verify_agents_imports.py (the recipe line was only read, not run)Openneeds-verification
Difficulty 1/5 Under an hour Newbie friendliness 76/100
EchoTools/nevr-runtime#1322 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 86/100
tenstorrent/tt-metal#63191 ·
Maintainers usually reply within 1 day
-
bug status/untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
karakeep-app/karakeep#3246 ·
Maintainers usually reply within 1 day
-
fix(server-update): termul-server --check-update fails with "failed to decode minisign signature" (manifest signature is base64-wrapped)Possibly taken A pull request linked to this issue is open or already merged. Openbug linux priority-medium to-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gnoviawan/termul#1557 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hyperledger-identus/docs#290 ·