Skip to content

Conversation

Sergio0694
Copy link
Member

This PR bumps the version of all packages to 8.2.1.

PR Checklist

  • Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
  • Based off latest main branch of toolkit
  • PR doesn't include merge commits (always rebase on top of our main, if needed)
  • Tested code with current supported SDKs
  • Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Header has been added to all new source files (run build/UpdateHeaders.bat)
  • Contains NO breaking changes
  • Every new API (including internal ones) has full XML docs
  • Code follows all style conventions

@Sergio0694 Sergio0694 added CI/pipeline 🔬 Some changes or issues related to CI infrastructure nuget 📦 Changes or issues related to NuGet publishing labels May 7, 2023
@Sergio0694
Copy link
Member Author

@Arlodotexe do you have any idea why the CI is failing here? I mean it seems some unit tests (which end up printing the assembly version) are still displaying 8.2.0, not 8.2.1, but why is that? I did the same changes last time (#635) and it worked?

@Sergio0694 Sergio0694 requested a review from Arlodotexe May 7, 2023 13:41
@Sergio0694 Sergio0694 force-pushed the dev/bump-version-8.2.1 branch 2 times, most recently from 2e7200e to 12877c2 Compare May 10, 2023 12:03
@Sergio0694 Sergio0694 force-pushed the dev/bump-version-8.2.1 branch from 12877c2 to e646a41 Compare May 10, 2023 14:29
@Sergio0694 Sergio0694 merged commit c5e8445 into main May 10, 2023
@delete-merged-branch delete-merged-branch bot deleted the dev/bump-version-8.2.1 branch May 10, 2023 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/pipeline 🔬 Some changes or issues related to CI infrastructure nuget 📦 Changes or issues related to NuGet publishing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant