Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ All notable changes to this package are documented in this file.

## Unreleased

## 1.2.0 - 2026-06-01

### Added

- Added integration docs for using this package with `ui-style-kit-css` and its `interactive-surface-bridge` export.
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -209,7 +209,7 @@ Release checklist:
2. Bump `version` in `package.json`.
3. Update `CHANGELOG.md`.
4. Push to `main`.
5. Create and publish a GitHub Release tag (for example `v1.1.5`).
5. Create and publish a GitHub Release tag (for example `v1.2.0`).
6. Verify the `Publish to npm` workflow succeeds.
7. Verify CDN availability:
- `https://cdn.jsdelivr.net/npm/interactive-surface-css@<version>/interactive-surface.css`
Expand Down
11 changes: 6 additions & 5 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1450,8 +1450,8 @@ <h2>README and wiki links</h2>
CDN:

```html
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/interactive-surface-css@1.1.5/interactive-surface.css" />
<link rel="stylesheet" href="https://unpkg.com/interactive-surface-css@1.1.5/interactive-surface.css" />
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/interactive-surface-css@1.2.0/interactive-surface.css" />
<link rel="stylesheet" href="https://unpkg.com/interactive-surface-css@1.2.0/interactive-surface.css" />
```

## Quick Start
Expand Down Expand Up @@ -1531,6 +1531,7 @@ <h2>README and wiki links</h2>
## Testing

```bash
npm run check:no-hex-colors
npm run lint:css
npm test
npm run test:chromium
Expand All @@ -1547,11 +1548,11 @@ <h2>README and wiki links</h2>
2. Bump `version` in `package.json`.
3. Update `CHANGELOG.md`.
4. Push to `main`.
5. Create and publish a GitHub Release tag (for example `v1.1.4`).
5. Create and publish a GitHub Release tag (for example `v1.2.0`).
6. Verify the `Publish to npm` workflow succeeds.
7. Verify CDN availability:
- `https://cdn.jsdelivr.net/npm/interactive-surface-css@1.1.4/interactive-surface.css`
- `https://unpkg.com/interactive-surface-css@1.1.4/interactive-surface.css`
- `https://cdn.jsdelivr.net/npm/interactive-surface-css@1.2.0/interactive-surface.css`
- `https://unpkg.com/interactive-surface-css@1.2.0/interactive-surface.css`

Manual fallback:

Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "interactive-surface-css",
"version": "1.1.5",
"version": "1.2.0",
"description": "A framework-agnostic, accessible CSS interaction primitive for buttons, cards, and icon controls with token-driven theming.",
"keywords": [
"css",
Expand Down
4 changes: 2 additions & 2 deletions wiki/Home.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,8 @@ Interactive Surface CSS centralizes that logic into a single reusable primitive:
- **JS entry:** `index.js` (imports the stylesheet)
- **Demo/customization page:** `index.html`
- **License:** MIT
- **Current version in repo:** `1.1.5`
- **Release tag:** `v1.1.5`
- **Current version in repo:** `1.2.0`
- **Release tag:** `v1.2.0`

## Documentation map

Expand Down
2 changes: 1 addition & 1 deletion wiki/Publishing-and-Releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ npm run pack:dry
```

5. Push changes to `main`.
6. Create and publish a GitHub Release for that version tag (for example `v1.1.5`).
6. Create and publish a GitHub Release for that version tag (for example `v1.2.0`).
7. Confirm `Publish to npm` workflow succeeds.
8. Verify distribution:

Expand Down