Skip to content
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

Jump to bottom

OSOE-400: Auto-generate next version number when publishing NuGet packages #787

Merged
merged 17 commits into from
Jun 12, 2024
Merged

OSOE-400: Auto-generate next version number when publishing NuGet packages #787

merged 17 commits into from
Jun 12, 2024

Conversation

AydinE
Copy link
Contributor

@AydinE AydinE commented Jun 5, 2024 •
edited by jira bot
Loading

@github-actions github-actions bot changed the title OSOE-440: Auto-generate next version number when publishing NuGet packages OSOE-400: OSOE-440: Auto-generate next version number when publishing NuGet packages Jun 5, 2024
@AydinE AydinE changed the title OSOE-400: OSOE-440: Auto-generate next version number when publishing NuGet packages OSOE-400: Auto-generate next version number when publishing NuGet packages Jun 5, 2024
@AydinE AydinE mentioned this pull request Jun 5, 2024
Closed
@github-actions GitHub Actions

This comment has been minimized.

Sign in to view
@github-actions GitHub Actions

This comment has been minimized.

Sign in to view
@github-actions GitHub Actions

This comment has been minimized.

Sign in to view
sarahelsaig
sarahelsaig requested changes Jun 11, 2024
View reviewed changes
Get-Solution-Projects.ps1 Outdated Show resolved Hide resolved
Get-Solution-Projects.ps1 Outdated Show resolved Hide resolved
Get-Solution-Projects.ps1 Outdated Show resolved Hide resolved
Update-References.ps1 Outdated Show resolved Hide resolved
Update-References.ps1 Outdated Show resolved Hide resolved
VNext.ps1 Outdated Show resolved Hide resolved
Releasing.md Outdated Show resolved Hide resolved
Releasing.md Outdated Show resolved Hide resolved
Releasing.md Outdated Show resolved Hide resolved
VNext.ps1 Outdated Show resolved Hide resolved
@AydinE
Copy link
Contributor Author

AydinE commented Jun 12, 2024

I believe I have addressed all of the points, since implementing your suggestion of using dotnet sln list which is obviously much cleaner I have decided the Get-Solution-Projects script was no longer needed so this is now removed.

@sarahelsaig sarahelsaig merged commit a67301b into dev Jun 12, 2024
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sarahelsaig sarahelsaig sarahelsaig requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@AydinE @sarahelsaig @LombiqBot