Skip to content

DAG-2605: Negiligible change to trigger/fix release pipeline #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
trahman1318 merged 1 commit into from
May 25, 2023
Merged

DAG-2605: Negiligible change to trigger/fix release pipeline #66

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Changelog

## 0.7.8 - 2022-05-25
Copy link
Contributor

@namazgurbanovmdb namazgurbanovmdb May 25, 2023

Choose a reason for hiding this comment

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

Was this the only place that was missed? I believe the version should be updated in more files.

Copy link
Contributor Author

@trahman1318 trahman1318 May 25, 2023

Choose a reason for hiding this comment

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

The "real" v0.7.8 code & changes are in this commit. This is just a follow-up commit.

This PR doesn't do anything and is a potential workaround. I'm stuck in a weird spot where I can't generate a new mongo-task-generator release for some reason.

I have this commit which is the "real commit" & was approved by DAG.

I then realized I had the change log wrong, so I made this followup commit. Since it was just a one line doc change, I just force merged with the "squash & merge button". After that commit, I have been unable to create a new release.
image

I get the following error:
https://github.com/mongodb/mongo-task-generator/actions/runs/5084796697/jobs/9137591223
image

I tried using different tag names that haven't been used yet, but still get the same error.

I figured it might have something to do with my force merging so I made this PR in case this is the solution. If there's another way to do this, I can try that too. I'm open to ideas.

Copy link
Contributor Author

@trahman1318 trahman1318 May 25, 2023

Choose a reason for hiding this comment

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

Also put some info in the slack channel but basically says the same thing: https://mongodb.slack.com/archives/C036F3YQ796/p1685051723965299

* Update burn in tags API to accommodate all required and suggested build variants.
* Update burn in tags API to accommodate all required and suggested buildvariants.

## 0.7.7 - 2022-05-08
* Make generated multiversion tasks explicit.
Expand Down