Skip to content

Fix milestone reading in update.py - #810

Draft
sagudev wants to merge 1 commit into
mainfrom
sagudev-patch-10
Draft

Fix milestone reading in update.py#810
sagudev wants to merge 1 commit into
mainfrom
sagudev-patch-10

Conversation

@sagudev

@sagudev sagudev commented Sep 2, 2026

Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: Sam <16504129+sagudev@users.noreply.github.com>
@sagudev

sagudev commented Sep 2, 2026

Copy link
Copy Markdown
Member Author

Uh oh, I think I did a mistake here. Usually I just remove source tags/release and retrigger CI run from fix branch to test it. But now with immutable releases they got deleted only from UI, but they still exist so CI cannot push them anew. Is disabling immutable releases for this repo temporary possible solution or did I just permanently mess things up? cc @jschwe

@jdm

jdm commented Sep 2, 2026

Copy link
Copy Markdown
Member

It's possible to disable it. I've turned it off.

@sagudev

sagudev commented Sep 2, 2026

Copy link
Copy Markdown
Member Author

It's possible to disable it. I've turned it off.

Yeah, but that's just for new releases I think. Old are still immutable: https://github.com/servo/mozjs/actions/runs/33642340739/job/100297584084#step:6:33

@jdm

jdm commented Sep 2, 2026

Copy link
Copy Markdown
Member

Yeah, I don't see anything about the release through the gh tool either :<

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants