kbase / kbase-ui

kbase-ui components

MIT License

10 stars 22 forks source link

Prepare release 2.6.4 #1608

Closed eapearson closed 2 years ago

eapearson commented 2 years ago

Pull Request to prepare release 2.6.4 UIP-9

Description

This set of changes paves the way for release 2.6.4 in the traditional manner, through release notes and stamping of the version in the codebase.

Issues Resolved

https://kbase-jira.atlassian.net/browse/UIP-9
[x] Added the Jira Tickets to the title of the PR e.g. (PTV-XXX fixes a terrible bug)
[-] Added the Github Issue to the title of the PR e.g. (PTV-XXX adds an awesome feature)

Testing Instructions

This PR has been the target of the kbase-ui integration tests.

[x] Tests pass locally
[x] Tests pass in github actions
[x] Manually verified that changes area available (by spinning up an instance and navigating to X to see Y)

Dev Checklist

[-] Code follows the guidelines at https://sites.google.com/truss.works/kbasetruss/development
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[-] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Integration tests have been run and fully pass (only when preparing a release)
[x] I have run run the code quality script against the codebase (also done implicitly during a build)

Release Notes

[x] Ensure there is an "upcoming release notes" file located in release-notes/RELEASE_NOTES_NEXT.md
[x] Add relevant notes to this document

Release

[x] Bump version in config/release.yml
[x] Rename release-notes/RELEASE_NOTES_NEXT.md to the appropriate release
[x] Add release notes document to the release notes index release-notes/index.md