-
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
[Feature]: Add a workflow that checks for package dependency updates and auto-updates #91
Labels
Projects
Milestone
Comments
janechu
added
1
Estimate (days)
area:dev-ops
Pertains to build, CI, and other dev-ops work
and removed
status:triage
New issue - needs triage
labels
Nov 5, 2021
3 tasks
janechu
added a commit
that referenced
this issue
Nov 11, 2021
…e branch when FAST Tooling dependencies are updated (#100) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This automated job rubs 1 hour after the FAST Tooling publish. It will check to see if the versions have been updated and if so will update them and run the script to generate new changelog versions for the "What's New" feature. This should cut down on the possibility that these changes are not added correctly, and that they can now be done in an automated fashion. I have also enabled this for dispatch should it be necessary. ### 🎫 Issues <!--- List and link relevant issues here using the keyword "closes" if this PR will close an issue, eg. closes #411 --> Closes #91 ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [x] I have tested my changes. - [x] 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. --> - See if this works, the individual pieces have been tested however the full workflow will need to be checked after packages have been released from FAST Tooling
3 tasks
janechu
added a commit
that referenced
this issue
Nov 17, 2021
…es (#110) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This is a follow up on #91, it appears that the PAT must have SSO authorization for Microsoft organization scoped repositories. Additionally the installation step was skipped in the workflow and has now been added. ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [x] I have tested my changes. - [x] 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. --> - Run this with a manual dispatch as a check, if there are no file updates to commit this may need to wait until tooling packages are updated.
janechu
added a commit
that referenced
this issue
Feb 28, 2022
…e branch when FAST Tooling dependencies are updated (#100) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This automated job rubs 1 hour after the FAST Tooling publish. It will check to see if the versions have been updated and if so will update them and run the script to generate new changelog versions for the "What's New" feature. This should cut down on the possibility that these changes are not added correctly, and that they can now be done in an automated fashion. I have also enabled this for dispatch should it be necessary. ### 🎫 Issues <!--- List and link relevant issues here using the keyword "closes" if this PR will close an issue, eg. closes #411 --> Closes #91 ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [x] I have tested my changes. - [x] 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. --> - See if this works, the individual pieces have been tested however the full workflow will need to be checked after packages have been released from FAST Tooling
janechu
added a commit
that referenced
this issue
Feb 28, 2022
…es (#110) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This is a follow up on #91, it appears that the PAT must have SSO authorization for Microsoft organization scoped repositories. Additionally the installation step was skipped in the workflow and has now been added. ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [x] I have tested my changes. - [x] 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. --> - Run this with a manual dispatch as a check, if there are no file updates to commit this may need to wait until tooling packages are updated.
janechu
added a commit
that referenced
this issue
Feb 28, 2022
…e branch when FAST Tooling dependencies are updated (#100) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This automated job rubs 1 hour after the FAST Tooling publish. It will check to see if the versions have been updated and if so will update them and run the script to generate new changelog versions for the "What's New" feature. This should cut down on the possibility that these changes are not added correctly, and that they can now be done in an automated fashion. I have also enabled this for dispatch should it be necessary. ### 🎫 Issues <!--- List and link relevant issues here using the keyword "closes" if this PR will close an issue, eg. closes #411 --> Closes #91 ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [x] I have tested my changes. - [x] 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. --> - See if this works, the individual pieces have been tested however the full workflow will need to be checked after packages have been released from FAST Tooling
janechu
added a commit
that referenced
this issue
Feb 28, 2022
…es (#110) # Pull Request ## 📖 Description <!--- Provide some background and a description of your work. --> This is a follow up on #91, it appears that the PAT must have SSO authorization for Microsoft organization scoped repositories. Additionally the installation step was skipped in the workflow and has now been added. ## ✅ Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have added tests for my changes. - [x] I have tested my changes. - [x] 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. --> - Run this with a manual dispatch as a check, if there are no file updates to commit this may need to wait until tooling packages are updated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Summary
This feature would add a github workflow that runs a scheduled cron job at the same interval as the publish in FAST tooling, an hour later. It should:
convert:version-files
scripts to update the version filesOther requirements:
The text was updated successfully, but these errors were encountered: