concourse / concourse/github-release-resource
filter for releases by age
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 57
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
A commonly advised heuristic to protect against supply chain attacks is to wait N days (e.g. N=3 or N=7) before deploying a new upstream release.
Describe the solution you'd like
It would be nice if the resource would offer a configuration option that makes it ignore releases whose age is below the configured threshold.
Describe alternatives you've considered
No response
Additional context
No response
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
No files or tests are named in the issue. Start by locating the resource's configuration handling and release-selection entry points, then inspect existing tests for release filtering. Done means a configured age threshold causes releases younger than that threshold to be ignored, while older releases remain eligible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100