Merge branch 'master' into feature/component-data-table

.github/workflows/chromatic.yaml

@@ -7,6 +7,7 @@ on:
 
 jobs:
   chromatic:
+    if: false # Temporarily disable until https://github.com/fortanix/baklava/issues/81 is resolved
     name: Run Chromatic
     runs-on: ubuntu-latest
     steps:

.github/workflows/ci.yaml

@@ -30,3 +30,4 @@ jobs:
     #- run: npm run build --if-present
     - run: npm run verify verify:source
     - run: npm test
+    - run: cd tests/installation && npm ci && npm test

.storybook/preview.tsx

@@ -26,7 +26,6 @@ const preview = {
             'Colors',
             'Typography',
             'Iconography',
-            'Change log',
           ],
           'typography',
           [
@@ -63,10 +62,13 @@ const preview = {
             ],
             'overlays',
             [
+              'ModalProvider',
+              'SpinnerModal',
+              'DialogModal',
               'Tooltip',
               'TooltipProvider',
-              'Dropdown',
-              'Modal',
+              'DropdownMenu',
+              'Toast',
             ],
             'lists',
             [

CHANGELOG.md

@@ -1,6 +1,4 @@
 
 # Change Log
 
-**v1.0.0**
-
-* Initial release.
+See [releases](https://github.com/fortanix/baklava/releases).

CONTRIBUTING.md

@@ -40,3 +40,30 @@ To create a new release:
   - Hit "Publish the release".
 
 - Once the release has been created, a GitHub Actions workflow will automatically run to publish this release to npm.
+
+
+**Script:**
+
+```shell
+VERSION=x.y.z
+git co -b release/v${VERSION}
+sed -i '' "s/version: '.*'/version: '${VERSION}'/" package.json.js
+npm run install-project
+git add package.json.js package.json package-lock.json
+git ci -m "Release v${VERSION}"
+git push -u origin HEAD
+npm run automate github:create-release-pr
+# Follow instructions from above command
+```
+
+## Publishing to npm
+
+To publish to npm:
+
+```shell
+npm publish --scope=@fortanix --access=public --dry-run # --tag=beta
+```
+
+Set the --tag as appropriate: beta for beta releases, or remove the --tag if you want to publish a stable release. Remove the --dry-run once you’ve confirmed there are no issues.
+
+**Note: you rarely need to do this manually. Instead, see the "Release workflow" above, which will trigger an npm publish automatically upon creation of a GitHub release.**

app/lib.ts

@@ -62,9 +62,11 @@ export { Stepper } from '../src/components/navigations/Stepper/Stepper.tsx';
 export { Tab, Tabs } from '../src/components/navigations/Tabs/Tabs.tsx';
 
 // Overlays
+export { ModalProvider } from '../src/components/overlays/ModalProvider/ModalProvider.tsx';
+export { SpinnerModal } from '../src/components/overlays/SpinnerModal/SpinnerModal.tsx';
+export { DialogModal } from '../src/components/overlays/DialogModal/DialogModal.tsx';
 export { DropdownMenu } from '../src/components/overlays/DropdownMenu/DropdownMenu.tsx';
 export { DropdownMenuProvider } from '../src/components/overlays/DropdownMenu/DropdownMenuProvider.tsx';
-export { Modal } from '../src/components/overlays/Modal/Modal.tsx';
 export { type ToastContent, ToastProvider, ToastMessage } from '../src/components/overlays/Toast/Toast.tsx';
 export { Tooltip } from '../src/components/overlays/Tooltip/Tooltip.tsx';
 export { TooltipProvider } from '../src/components/overlays/Tooltip/TooltipProvider.tsx';

biome.jsonc

@@ -24,9 +24,11 @@
   "linter": {
     "enabled": true,
     "include": ["app/**/*", "src/**/*", "tests/**/*"],
+
     "ignore": [
-      "src/components/tables/MultiSearch/MultiSearch.tsx" // Ignore for now (need to focus on type errors first)
-    ],
+      "src/components/tables/MultiSearch/MultiSearch.tsx", // Ignore for now (need to focus on type errors first)
+      "tests/installation/**/*"
+  ],
     "rules": {
       "recommended": true,
       "complexity": {