Skip to content

Conversation

ankit--sethi
Copy link
Contributor

@ankit--sethi ankit--sethi commented Aug 20, 2025

Updating Jakarta Mail by 1.6.4 -> 1.6.8 to absorb a few bug fixes

@ankit--sethi ankit--sethi requested a review from a team as a code owner August 20, 2025 16:17
@ankit--sethi ankit--sethi added the :Security/Security Security issues without another label label Aug 20, 2025
@elasticsearchmachine elasticsearchmachine added Team:Security Meta label for security team v9.2.0 labels Aug 20, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@ankit--sethi ankit--sethi added v9.1.0 v9.0.7 v8.18.6 v9.1.4 auto-backport Automatically create backport pull requests when merged >non-issue and removed v9.1.0 labels Aug 20, 2025
@ankit--sethi ankit--sethi merged commit b3f8ea8 into elastic:main Aug 20, 2025
34 checks passed
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.18
9.1
9.0

ankit--sethi added a commit to ankit--sethi/elasticsearch that referenced this pull request Aug 20, 2025
ankit--sethi added a commit to ankit--sethi/elasticsearch that referenced this pull request Aug 20, 2025
ankit--sethi added a commit to ankit--sethi/elasticsearch that referenced this pull request Aug 20, 2025
elasticsearchmachine pushed a commit that referenced this pull request Aug 20, 2025
@breskeby
Copy link
Contributor

Can we keep our PRs a bit more descriptive than "bump version" or "bump"?

elasticsearchmachine pushed a commit that referenced this pull request Aug 20, 2025
elasticsearchmachine pushed a commit that referenced this pull request Aug 20, 2025
@slobodanadamovic
Copy link
Contributor

Can we keep our PRs a bit more descriptive than "bump version" or "bump"?

++ to adding more context to the PR title and description. Also, please don't merge version upgrades without peer review and approval.

@ankit--sethi
Copy link
Contributor Author

Can we keep our PRs a bit more descriptive than "bump version" or "bump"?

my understanding was we want to keep things light on details in the PR if the version bump involves security considerations.

@slobodanadamovic
Copy link
Contributor

Can we keep our PRs a bit more descriptive than "bump version" or "bump"?

my understanding was we want to keep things light on details in the PR if the version bump involves security considerations.

That's true. We don't have to get into details why, but we should mention what we are updating and to which version.

@ankit--sethi ankit--sethi changed the title bump version bump Jakarta Mail Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >non-issue :Security/Security Security issues without another label Team:Security Meta label for security team v8.18.6 v9.0.7 v9.1.4 v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants