Closed khebhut[bot] closed 3 years ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign michaelclifford after the PR has been reviewed.
You can assign the PR to them by writing /assign @michaelclifford
in a comment when ready.
The full list of commands accepted by this bot can be found here.
@harshad16 shouldn't it have been v0.0.2 since this is a new patch release?
shouldn't it have been v0.0.2 since this is a new patch release?
@Shreyanand , for the bot , this is the source of truth https://github.com/aicoe-aiops/time-series/blob/1499eeddcd6884c26279bb8430f0f1671de46e8b/setup.py#L5 , while updating versions. it doesn't rely on existing tags, as that get updated and delete.
This values is what the bot try to keep up.
i would suggest, closing this pr and the issue.
fix this https://github.com/aicoe-aiops/time-series/blob/1499eeddcd6884c26279bb8430f0f1671de46e8b/setup.py#L5 value manually to v0.0.1
and then opening the patch release request again,
shouldn't it have been v0.0.2 since this is a new patch release?
@Shreyanand , for the bot , this is the source of truth
https://github.com/aicoe-aiops/time-series/blob/1499eeddcd6884c26279bb8430f0f1671de46e8b/setup.py#L5
, while updating versions. it doesn't rely on existing tags, as that get updated and delete. This values is what the bot try to keep up. i would suggest, closing this pr and the issue. fix this
https://github.com/aicoe-aiops/time-series/blob/1499eeddcd6884c26279bb8430f0f1671de46e8b/setup.py#L5
value manually to
v0.0.1
and then opening the patch release request again,
Aah ok, that makes sense, thanks :)
Hey, @Shreyanand!
Opening this PR to fix the last release.
WARNING NOTE The release version mentioned in the source-code couldn't be found in git tags, hence the release is created from the start. If that is not the right behavior:
Create a new release issue.
Closes: #44