WIP: feat(ci): Add a workflow to update flake hashes #947
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#947
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Shuroii/continuwuity:flake-updater"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This workflow is intended to be ran as dispatch whenever the rocksdb fork changes!
Other than that, it'll run on any toolchain changes (rust-toolchain.toml, Cargo.lock, Cargo.toml) and update the relevant hash accordingly.
This is built to work on #945 so maybe wait on that to get merged before merging this. It won't actually break without that getting merged, but it will run a
nix build
without first ensuring it won't actually build continuwuity, which might not be desirable.Oh, one more thing; if this is ran as a dispatch on main, it'll fail to commit. Only run this on branches that have an open pull request! I can make it make a PR like renovate, where it'll edit an existing one if it finds one, but that means making this workflow at least twice the size, as well as giving it an auth token.
fd01c49099
to6c69c3e51b
6c69c3e51b
to3216817273
a743c4fd3c
to10630214d8
@tcpipuk do you happen to know the version of the runner? For some reason it's not recognizing the
forgejo
environment namespace and I got some weird errors regarding it not recognizing something as simple aswhere it errors at
run:
.My workflow doesn't appear to pass schema validation here despite it doing so on my runner (v9.1.1).
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.