Release v1.0.1 with scoped package name and workflow updates#28
Merged
Conversation
Update version numbers to 1.0.0 across all CSS files and add MIT license information to documentation headers. Also add author attribution (ComfortCSS) to main entry points.
Mark the first stable release of the library.
Simplify the output filename from 'comfort-css-reset.min.css' to 'reset.min.css'. Update all references in package.json, build script, and documentation.
Release V1.0.0
Change package name to a scoped format (@comfortcss/reset). Scoped packages help organize related packages under a namespace and reduce naming conflicts on the npm registry.
Rename package to @comfortcss/reset
Updated README documentation to reflect the new scoped package name (@comfort-css/reset) and GitHub repository installation method (comfortcss/reset:1.0.0). This affects all installation and import examples in the documentation.
Update package name and import paths
Add GitHub Actions workflow to automatically publish the package to npm on release or manual trigger. The workflow includes dependency installation, build, and test steps before publishing with provenance.
Rename package from @comfort-css/reset to @comfortcss/reset and update module paths from src/core to modules. Add repository metadata, npm lifecycle scripts (prepare, prepublishOnly), public access configuration, and comprehensive exports field for multiple entry points.
Update v1.0.1
Update the Node.js version used in the publish workflow from 27.x to 22.x for better compatibility and stability.
Downgrade Node.js to 22.x in publish workflow
Commit package-lock.json to enable reproducible installs and ensure all developers use consistent dependency versions. Remove package-lock.json from .gitignore.
Track package-lock.json in version control
Comment out the test step in the npm publish workflow. This removes the test execution from the automated publishing pipeline.
Comment out the build step in the GitHub Actions publish workflow.
Disable build step in publish workflow
Release patch version 1.0.1. Updates version information across package.json, CSS source files, and README with generic version placeholder.
Bump version to 1.0.1
Add --access public to the npm publish step in .github/workflows/publish.yml so packages are published publicly from CI. Keeps the existing --provenance flag. This ensures scoped packages are published with public visibility instead of defaulting to restricted/private.
Set npm publish access to public
Update .github/workflows/publish.yml to use Node.js 24.x instead of 22.x for the publish job. The setup-node action version and registry-url remain unchanged; install step still uses npm ci.
Bump Node.js version in publish workflow to 24.x
Adjust README import examples to use the package entry points. Revise package.json: normalize repository URL casing, add style exports for the package and ./reset, remove the previous ./modules default export and redundant dist mapping, and map ./modules/* to ./src/*. These changes expose the bundled CSS as the package style entry and simplify module path exports.
Update package exports and README imports
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.