Skip to content

Conversation

naitoh
Copy link
Contributor

@naitoh naitoh commented Sep 17, 2025

No description provided.

@naitoh naitoh requested a review from a team as a code owner September 17, 2025 06:06
@naitoh naitoh force-pushed the rexml-cve-2025-58767 branch from 2336487 to 54a7cd4 Compare September 17, 2025 06:09
Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@mame @hsbt Could you merge this?

Copy link
Member

@hsbt hsbt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks always 👍

@hsbt hsbt merged commit b933697 into ruby:master Sep 17, 2025
1 check passed
@naitoh naitoh deleted the rexml-cve-2025-58767 branch September 17, 2025 06:31
@kou
Copy link
Member

kou commented Sep 17, 2025

Ah, sorry... This article wasn't published because the date uses a future date:

https://github.com/ruby/www.ruby-lang.org/actions/runs/17788666874/job/50560893546#step:5:13

          Skipping: en/news/_posts/2025-09-18-dos-rexml-cve-2025-58767.md has a future date

@hsbt Could you re-run the job tomorrow (2025-09-18T12:00:00+09:00) or later?

@hsbt
Copy link
Member

hsbt commented Sep 17, 2025

or simply modified publish data like 2025-09-17T6:00:00+09:00? I'm okay to re-run at today's night.

@kou
Copy link
Member

kou commented Sep 17, 2025

@naitoh Which approach do you prefer?

@naitoh
Copy link
Contributor Author

naitoh commented Sep 17, 2025

@hsbt @kou

Could you re-run the job tomorrow (2025-09-18T12:00:00+09:00) or later?

Please, this.

@hsbt
Copy link
Member

hsbt commented Sep 17, 2025

The publish date is 2025-09-18 03:00:00 +0000. It means this advisory will publish 9/18 12:00 JST. I'm not sure that time is intentional. But I will re-run that after 12:00 JST today.

@kou
Copy link
Member

kou commented Sep 18, 2025

Yes. The publish date isn't strictly correct. We just don't care about strict date.

FYI: We can merge any other PR such as #3623 instead of re-run the job to publish this article.

@hsbt
Copy link
Member

hsbt commented Sep 18, 2025

@kou
Copy link
Member

kou commented Sep 18, 2025

Thanks!

1 similar comment
@naitoh
Copy link
Contributor Author

naitoh commented Sep 18, 2025

Thanks!

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