Skip to content

Conversation

abdulsattar
Copy link
Collaborator

@abdulsattar abdulsattar commented Aug 8, 2025

What does this PR do?

What issues does this PR fix or reference?

@W-19293277@

@abdulsattar abdulsattar requested review from a team as code owners August 8, 2025 17:11
@abdulsattar abdulsattar changed the title fix: bump version number on next W-19293277: bump version number on next Aug 8, 2025
},
{
"versionNumber": "64.0",
"tagName": "prerelease"
Copy link
Collaborator

Choose a reason for hiding this comment

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

The above need updates too, right?
64.0 is latest
65.0 is prerelease

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Not yet, after SB0, right?

Copy link
Collaborator

Choose a reason for hiding this comment

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

64.0 is the latest as 256 is the release across all of production.

65.0 > yes, SB0 scheduled for 8/11/2025. So you can do it today, its close enough.

"target": {
"versionNumber": "65.0",
"versionNumber": "66.0",
"matchingDevServerVersion": "~13.0.27"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you please bump the dependency version and matching devServerVersion in a follow up PR?

@abdulsattar abdulsattar merged commit 9644d76 into main Aug 8, 2025
15 of 17 checks passed
@abdulsattar abdulsattar deleted the abdulsattar/bump-version-number branch August 8, 2025 17:51
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