@royaloperahouse/harmonic 0.13.4 → 0.14.0

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## [0.14.0]
+- CastFilter: Add CastFilter component
+- Swipe: Update focus padding
+
 ## [0.13.4]
 - Footer: internal links open in the same tab
 

package/README.GIT

@@ -24,17 +24,33 @@ The Storybook for the latest version of the library is hosted at [Storybook - Ha
   
     *AWS 'Your Applications' page -> 'Royal Opera House' -> 'Developer Access' -> 'Command line or programmatic access'*
 
-* **To deploy a preview** for demo / QA you will need the `CHROMATIC_PROJECT_TOKEN` -- find this in 1Password. Creating your own Chromatic account is advised if multiple builds are necessary.
+* **To deploy a preview** for demo / QA you will need:
+
+  * A Chromatic account with a **Developer** role in the `roh-ml` project in Chromatic
+    * [Mari Lovell](mari.lovell@roh.org.uk) is the current owner of this project, you can contact her to invite you
+  * The `CHROMATIC_PROJECT_TOKEN` -- find this in 1Password or ask the project owner.
 
 
 * **To enable publishing to the NPM package**:
   * Create account / log in to NPM
   * Ask a colleague with admin rights to be added as a contributer 
   * Generate your own ROH `NPM_TOKEN` (store this token in 1Password)
+  * Set up Two-Factor Authentication for NPM, as you will be prompted by the publishing script
 
 
 ## Versioning
 ---
+> NOTE: The following applies while the Harmonic project is in Alpha (before a version 1.0.0 release)
+
+We are **not** yet using semantic versioning.
+
+When proposing changes to the Harmonic library, increment the patch version (the last number) by one, **only** in the changelog (alternatively, leave the version in the changelog as TBC) along with a note about your changes.
+
+Only increment the version in the package.json for releasing snapshots.
+
+Once your changes are merged to the main branch and released in a new version, the release manager will be responsible for incrementing that release version.
+
+> NOTE: The following **may** apply once the Harmonic project is out of Alpha, but is subject to change before then.
 
 We use [Semantic Versioning](https://semver.org/) for Harmonic.
 
@@ -69,7 +85,7 @@ The server will hot-reload on most changes.
 
 You can deploy a release candidate, or work-in-progress to [Chromatic](https://www.chromatic.com/) for showcase or QA.
 
-**NOTE:** you will need the `CHROMATIC_PROJECT_TOKEN` as described in *Prerequisites* above.
+**NOTE:** you will need the `CHROMATIC_PROJECT_TOKEN` and to be invited as a contributor to the Harmonic project in Chromatic, as described in *Prerequisites* above.
 
 Either set the token as a shell variable or use a `.env` file in the `harmonic` root directory containing the token, as so:
 

package/dist/components/atoms/TextField/TextField.style.d.ts

@@ -7,4 +7,4 @@ export declare const Input: import("styled-components").StyledComponent<"input",
 export declare const ShowHideButton: import("styled-components").StyledComponent<"button", any, {}, never>;
 export declare const TextLabel: import("styled-components").StyledComponent<"div", any, Pick<ITextFieldProps, "darkMode">, never>;
 export declare const ErrorLabel: import("styled-components").StyledComponent<"div", any, Pick<ITextFieldProps, "darkMode">, never>;
-export declare const BodyCopyHarmonicWithWrapper: import("styled-components").StyledComponent<import("react").ForwardRefExoticComponent<import("../../../types/typography").ITaggedTypographyProps & import("react").RefAttributes<HTMLParagraphElement>>, any, {}, never>;
+export declare const BodyCopyHarmonicWithWrapper: import("styled-components").StyledComponent<({ children, size, color, className, bold, tag: Tag, ...props }: import("../../../types/typography").ITaggedTypographyProps) => import("react").JSX.Element, any, {}, never>;