Skip to content

Prepare release v0.53.1#87

Merged
shahrokni merged 1 commit intomainfrom
release-v0.54.0
Mar 10, 2026
Merged

Prepare release v0.53.1#87
shahrokni merged 1 commit intomainfrom
release-v0.54.0

Conversation

@shahrokni
Copy link
Contributor

@shahrokni shahrokni commented Mar 10, 2026

RELEASE 0.53.1

Description

@shahrokni shahrokni requested a review from a team as a code owner March 10, 2026 11:14
@Nexucis
Copy link
Member

Nexucis commented Mar 10, 2026

Considering you are going to release only bugfixes from what I can tell, you should actually release a patch (so v0.53.1) instead

@Nexucis
Copy link
Member

Nexucis commented Mar 10, 2026

and before that, you should upgrade the @perses-dev/core version to v0.53.0

@Nexucis
Copy link
Member

Nexucis commented Mar 10, 2026

Considering you are going to release only bugfixes from what I can tell, you should actually release a patch (so v0.53.1) instead

this is also because to avoid to maintain a compatibility matrix between perses and the shared packages, it's better if the version is synchronised at least for the minor version.

Meaning that if you are going to create a v0.54.0, then you will release perses/perses with a v0.54.0 containing this new version of the shared package.

@shahrokni
Copy link
Contributor Author

shahrokni commented Mar 10, 2026

Considering you are going to release only bugfixes from what I can tell, you should actually release a patch (so v0.53.1) instead

I have a backward compatible feature as well. Still 0.53.1?

add csv export util under plugin sys to be avilable to all plugins

@Nexucis
Copy link
Member

Nexucis commented Mar 10, 2026

yes this will be fine

Signed-off-by: Seyed Mahmoud SHAHROKNI <seyedmahmoud.shahrokni@amadeus.com>

Signed-off-by: Seyed Mahmoud SHAHROKNI <seyedmahmoud.shahrokni@amadeus.com>

Signed-off-by: Seyed Mahmoud SHAHROKNI <seyedmahmoud.shahrokni@amadeus.com>
@shahrokni shahrokni changed the title Prepare release v0.54.0 Prepare release v0.53.1 Mar 10, 2026
@shahrokni
Copy link
Contributor Author

shahrokni commented Mar 10, 2026

yes this will be fine

  1. Updated to 0.53.1
  2. Updated core dpendecy to 0.53.0
  3. updated README (Missing step)
  4. Commit message amended to mention 0.53.1
  5. I think If I change the branch name to 0.53.1, it will be a different PR, because I need to git checkout -b from this branch so the branch name is wrong. Since the branch will be removed after merge, would it be ok to keep it as it is?

@Nexucis
Copy link
Member

Nexucis commented Mar 10, 2026

I think If I change the branch name to 0.53.1, it will be a different PR, because I need to git checkout -b from this branch so the branch name is wrong. Since the branch will be removed after merge, would it be ok to keep it as it is?

the name of the branch does not matter, so you can keep this one

@shahrokni shahrokni requested a review from Nexucis March 10, 2026 12:22
@shahrokni
Copy link
Contributor Author

I think If I change the branch name to 0.53.1, it will be a different PR, because I need to git checkout -b from this branch so the branch name is wrong. Since the branch will be removed after merge, would it be ok to keep it as it is?

the name of the branch does not matter, so you can keep this one

Approved?

@shahrokni shahrokni merged commit 6bb6e09 into main Mar 10, 2026
15 of 17 checks passed
@shahrokni shahrokni deleted the release-v0.54.0 branch March 10, 2026 12:53
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