Skip to content

Conversation

@alilleybrinker
Copy link
Collaborator

No description provided.

We no longer use `git cliff` for generating changelogs, in fact
we moved away from a changelog file and toward release notes, so this
commit removes the `git cliff` configuration from the top-level
Cargo manifest. 

Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
This is mostly the same for us, but it's good to track the
latest version. See the Cargo docs for more [1].

[1]: https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions

Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
This bumps the versions of all top-level deps to their latest
patch versions, and notes any other top-level deps which are
behind by *more* than a patch version.

Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
@alilleybrinker alilleybrinker force-pushed the alilleybrinker/deps-bump branch from b885849 to 98ac778 Compare November 18, 2025 18:44
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
@alilleybrinker alilleybrinker force-pushed the alilleybrinker/deps-bump branch from 7736f7a to 126e359 Compare November 18, 2025 19:17
Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
@alilleybrinker alilleybrinker force-pushed the alilleybrinker/deps-bump branch from 126e359 to 82319c1 Compare November 18, 2025 19:22
@alilleybrinker alilleybrinker added this pull request to the merge queue Nov 18, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 18, 2025
@alilleybrinker alilleybrinker added this pull request to the merge queue Nov 18, 2025
@alilleybrinker
Copy link
Collaborator Author

Retrying merge. Looks like it failed due to the GitHub Git operations outage.

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 18, 2025
@alilleybrinker
Copy link
Collaborator Author

Merge queue failed because the macos-15-intel runner took too long and timed out (20 minutes). Retrying.

macos-15-intel runners are slow, but we want to keep them, so let's
try bumping the CI timeouts by 10 minutes to see if that lets them
finish successfully.

Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>
@alilleybrinker
Copy link
Collaborator Author

Bumped the timeout to 30 minutes to see if that's enough. Unfortunately, macos-15-intel runners are known to be slow and there's not much we can do about it.

actions/runner-images#12545

@alilleybrinker
Copy link
Collaborator Author

Okay, now the run tests are failing without any of that logic being changed from prior test runs. Will need to test further.

@alilleybrinker
Copy link
Collaborator Author

In local runs of the same command these download issues don't appear. Going to try another rerun on GitHub on the off chance this is a weird GitHub-specific issue, given that they had a big outage recently.

@alilleybrinker
Copy link
Collaborator Author

Ah, yup, fresh outage: https://www.githubstatus.com/incidents/cg3wwz9dw5dg

@alilleybrinker
Copy link
Collaborator Author

Okay, I am being driven slowly to insanity. GitHub claims the outage is resolved, but I still see one GitHub-hosted release artifact which I know exists, but which my action says it failed to download with an HTTP 503 error ("forbidden"). Soooo I think the outage is still happening, though now it's impacting one runner instead of three.

@alilleybrinker alilleybrinker merged commit b49bfd0 into main Nov 20, 2025
33 of 45 checks passed
@alilleybrinker
Copy link
Collaborator Author

Opted to just skip and merge, I'm tired of waiting for CI to not be broken.

@alilleybrinker alilleybrinker deleted the alilleybrinker/deps-bump branch November 21, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants