feat(ci): Add a workflow to update flake hashes #947
Jade
nex
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/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status/Blocked
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
5 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 buildwithout 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.
fd01c490996c69c3e51b6c69c3e51b3216817273a743c4fd3c10630214d8@tcpipuk do you happen to know the version of the runner? For some reason it's not recognizing the
forgejoenvironment 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).
WIP: feat(ci): Add a workflow to update flake hashesto feat(ci): Add a workflow to update flake hashes10630214d80396aa2cdb0396aa2cdb4454cec4aaSorry, the CI checks should be more reliable now we're not relying on GitHub!
The runner version is v9.1.1 (you can see it at the top of every Actions run in the "Set up job" step)
4454cec4aa4a57b3fe4cAh, the reason the build is failing is that you don't have access to the secret. I assume there has been a recent change in Forgejo permissions because we weren't having these issues before!
I've created #989 which I think should resolve this, just waiting for checks to pass (it won't 100% confirm whether it'll work for you, but I can at least ensure it won't break main branch before letting it loose!)
4a57b3fe4cb5fae111a4b5fae111a4c01c941bdaAlright, nearly there... I think #992 solves the one remaining issue with building a Docker image without logging into a Docker registry 😅
c01c941bda62c8cf582562c8cf5825ce68de93f7There we go! Completed artifacts on the CI run 👌
To test this, rebase #946 on top of it I think (or the other way around)
ce68de93f7f57c660ad6Got to rebase this again :3
f57c660ad6cf47986507cf479865079142978a15