You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @geoffreymcgill, because we are using changesets to cut releases we have PRs automatically created for our release tracking. The updated upload icon will be in 16.3.1 as seen in this PR. #735
Ashygee, I think you have the website publish workflow set for every push instead of every "release publish". So once the pull request for the upload icon was merged, the new icon reflected in the website while reporting version 16.3.0.
Now that release 16.3.1 occurred, the website is up-to-date (has 16.3.1 changes and report version 16.3.1). So I guess it is pushing a "latest" version before the version number is actually switched and, when the version string is bumped (with the release) the "push" with the version changes trigger again deployment and the site stays in sync with the reported version... until next pull request is merged. :)
In other words, the way the deploy is set up now will reflect current main in the website while reporting the latest full release version string, which made us some confusion about the upload icon and version it was included in.
The
v16.3.0
icons published on the website are not in sync with thev16.3.0
release tag.For example, see the
upload
icon on the website:... and here is the
upload
icon in themain
branch:... vs the
upload
icon in thev16.3.0
release tag:The text was updated successfully, but these errors were encountered: