Skip to content

Release 3.2.1#601

Open
CharlieTLe wants to merge 1 commit intomasterfrom
release-3.2.1
Open

Release 3.2.1#601
CharlieTLe wants to merge 1 commit intomasterfrom
release-3.2.1

Conversation

@CharlieTLe
Copy link
Copy Markdown
Member

Automated release PR for version 3.2.1

@nschad
Copy link
Copy Markdown
Collaborator

nschad commented Mar 2, 2026

@CharlieTLe did you open this? Why?

No right? I guess the CI creates a PR in your name :D. We should probably address that @kd7lxl

@kd7lxl
Copy link
Copy Markdown
Collaborator

kd7lxl commented Mar 2, 2026

@CharlieTLe did you open this? Why?

No right? I guess the CI creates a PR in your name :D. We should probably address that @kd7lxl

Due to the repo permissions, which I don't have access to, this is the best the admin would do. We have a slack thread about it

Signed-off-by: nschad <nschad@users.noreply.github.com>
@nschad
Copy link
Copy Markdown
Collaborator

nschad commented Apr 9, 2026

Can we close this? This doesn't do anything?

We only did CI related commits in the meanwhile: v3.2.0...master

@kd7lxl
Copy link
Copy Markdown
Collaborator

kd7lxl commented Apr 9, 2026

Can we close this? This doesn't do anything?

We only did CI related commits in the meanwhile: v3.2.0...master

It will continue to be updated with every commit until we feel it is worth merging, so I wouldn't close it.

If you have some time you could update the job to ignore CI-only commits, but the edge cases around that lead me to just leave it like it is.

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.

3 participants