Tits that damn safe-to-run tag
Tlets just remove that 
Till revert the thing and pr it
Tcuz this is causing more trouble than not
JToh nope
Tthat one was cuz you didnt bump the spec
Jhttps://github.com/ublue-os/packages/pull/300 this one is dangling too
Tso the action didnt know how t obuild it
JI didn't know I had to bump the spec
Tneed to fix the conflict here
Till actually do that right now, lemme just revert the thing
Tno worries its counter intuitive
Tgotta find some automated way of doing it
TTthere ya go
Tall the renovate ones should be fine i think
Tlets see
Jthis failure confuses me
Tits trying to build a non-existent spec
Tso it fails quietly
Tthen it fails cuz the build didnt run
Tits super dumb
Till add a check to make sure the specs that it tries to find actually exist so we dont get this weird error
Jok so can we just merge this or is it a systemic problem?
Junderstood
Tnothing wrong with your PR
Tcan be merged just fine
JJone more
Tlooks like it just needs a rebase
JTseems to be a small update, we might want to check out the commit changes between those
T@Kyle Gospo ?
Tany idea if this one blows up bazzite?
Jhttps://github.com/ublue-os/packages/pull/232 ugh man I thought we handled this last month
J
Toh man that also reminded me, all the bazzite spec files dont have the fancy renovate stuff
J@M2 can I get a final eyeball on this one? ^
MYeah that one is fine
Jwhat's the tldr on the key management on this?
Jdid we do the due diligence in 1password?
Mnew public key is in repo
Jor did we jorge it? 
Mbackup key is only stored in 1password and is not loaded into github secrets
Jok I'll put that in the issue and merge
Jta
MI believe we did that already as well
Mwe held off on merging because.... we wanted to make sure it works. But I guess we all just left comments