File tree Expand file tree Collapse file tree 3 files changed +19
-3
lines changed
Expand file tree Collapse file tree 3 files changed +19
-3
lines changed Original file line number Diff line number Diff line change @@ -5,13 +5,14 @@ SciReactUI Changelog
55--------------------
66
77### Added
8- - Breadcrumbs takes object for total control over names and links
8+ - Breadcrumbs take object array (CustomLink) for total control over names and links
99
1010### Fixed
1111- Stopped flicker between colour modes when starting an app in dark mode.
1212- Footer links stopped from moving on hover when only showing links.
1313- Footer links now correctly center horizontally, if needed.
1414- NavBar positions items correctly in multiple screen widths.
15+ - User hides id and name when on very small screens
1516
1617### Changed
1718- Footer links now align with copyright when there is no logo.
Original file line number Diff line number Diff line change 11{
22 "name" : " @diamondlightsource/sci-react-ui" ,
3- "version" : " 0.0.4a " ,
3+ "version" : " 0.1.0 " ,
44 "description" : " A theme and component library to make websites at scientific institutions simple to create." ,
55 "author" : " Diamond Light Source" ,
66 "license" : " ISC" ,
Original file line number Diff line number Diff line change @@ -122,4 +122,19 @@ pnpm pack
122122In the test app repo:
123123``` sh
124124pnpm install < path-to-this-app-folder> /diamondlightsource-sci-react-ui-0.0.1.tgz
125- ```
125+ ```
126+
127+ Publishing
128+ ----------
129+
130+ Steps needed when publishing a new version.
131+ - Create a new branch
132+ - Update the version in [ ./package.json] ( package.json )
133+ - Update the changelog in [ ./changelog.md] ( changelog.md ) with added/changed/fixed
134+ - Check this readme still makes sense with the new changes you are about to publish
135+ - Check the introduction file [ src/storybook/Introduction.mdx] ( src/storybook/Introduction.mdx ) in Storybook still makes sense
136+ - Now create a new git tag with a version number greater than the last.
137+ - Push the branch, get it reviewed and merge. It is now published!
138+
139+ Once publish, it's a good idea to increase the package version and add alpha, e.g "1.2.3a".
140+ And make a space at the top of the changelog to add future changes in, e.g. empty added/changed/fixed spaces.
You can’t perform that action at this time.
0 commit comments