Add workflow to update audit expiry
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
### Summary
After this [PR contribution](https://github.com/mi6/ic-ui-kit/pull/4178), we will have a script that we can manually run to update the audit expiry dates. However, these sometimes catch us out. It would be good if we could have a workflow that runs daily and checks if `npm run audit-expiry` fails, and then if it does, run the new `audit:update` script.
### 💬 Description
List of actions the workflow should do:
- Run `npm run audit-expiry`
- Run `npm run audit:update`
- Commit those changes to `chore(root)`
- Create a PR to develop
### 💰 Use value
It would save developers a job that happens monthly.
### 🚨 Urgency (low, medium or high)
Low
### Additional info
I've suggested running the workflow daily, but realistically if we keep adding a month to the date then the day won't actually change so we could just run it every 25th.
Looks like we can use schedule cron - https://jasonet.co/posts/scheduled-actions/
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 by inspecting the package scripts behind `npm run audit-expiry` and `npm run audit:update`, then review the repository's existing workflow conventions. Confirm the scheduled job runs on the intended cadence, updates expiry dates only when the check fails, commits the changes as `chore(root)`, and creates a PR targeting `develop`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100