-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Add the what's new feature which shows updates for past releases #67
Conversation
5726eca
to
0430f87
Compare
Azure Static Web Apps: Your stage site is ready! Visit it here: https://orange-mushroom-0d77ce210-67.centralus.azurestaticapps.net |
1 similar comment
Azure Static Web Apps: Your stage site is ready! Visit it here: https://orange-mushroom-0d77ce210-67.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://orange-mushroom-0d77ce210-67.centralus.azurestaticapps.net |
…idation and deploy (#68) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This causes the build step to build the release branch for the deployed artifact and not the PR branch that triggered the workflow. See: https://github.com/actions/checkout#usage ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [ ] I have tested my changes. - [ ] I have updated the project documentation to reflect my changes. ## ⏭ Next Steps <!--- If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next. --> This should enable PRs such as #67 to show the feature work in the deployed site.
Azure Static Web Apps: Your stage site is ready! Visit it here: https://orange-mushroom-0d77ce210-67.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-sand-02c786f10-67.centralus.azurestaticapps.net |
…idation and deploy (#68) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This causes the build step to build the release branch for the deployed artifact and not the PR branch that triggered the workflow. See: https://github.com/actions/checkout#usage ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [ ] I have tested my changes. - [ ] I have updated the project documentation to reflect my changes. ## ⏭ Next Steps <!--- If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next. --> This should enable PRs such as #67 to show the feature work in the deployed site.
* Add the what's new feature which shows updates for past releases * eslint fix Co-authored-by: Aaron Wentzel <16669785+awentzel@users.noreply.github.com>
Pull Request
📖 Description
This change:
@microsoft/fast-tooling
@microsoft/fast-tooling-react
@microsoft/fast-creator
The badge showing the version as there are no updates:
The button showing because there are updates and the modal can now be opened:
The dialog showing the updates:
👩💻 Reviewer Notes
After the first load of the site, if you want to view the dialog again, you will need to clean your local storage of the 3 keys that have been added to store the last version number.
✅ Checklist
General