@7365admin1/module-hygiene 1.7.0

package/.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

package/.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

package/.github/workflows/main.yml

@@ -0,0 +1,17 @@
+name: CI
+on:
+  push:
+    branches:
+      - "**"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+          cache: "yarn"
+      - run: yarn install --frozen-lockfile
+      - run: yarn lint && yarn build

package/.github/workflows/publish.yml

@@ -0,0 +1,39 @@
+name: Publish
+on:
+  workflow_run:
+    workflows: [CI]
+    branches: [main]
+    types: [completed]
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  publish:
+    if: ${{ github.event.workflow_run.conclusion == 'success' }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+          cache: "yarn" # Use yarn for caching
+          cache-dependency-path: yarn.lock # Cache Yarn lockfile
+
+      - run: yarn install --immutable # Install dependencies with immutable lockfile
+
+      - name: Create .npmrc for publishing
+        run: |
+          echo '//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}' > ~/.npmrc
+
+      - name: Create Release Pull Request or Publish
+        id: changesets
+        uses: changesets/action@v1
+        with:
+          publish: yarn release # Use yarn for publishing
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

package/CHANGELOG.md

@@ -0,0 +1,110 @@
+# @iservice365/module-hygiene
+
+## 1.7.0
+
+### Minor Changes
+
+- Hygiene Dashboard - Initial Release
+
+## 1.6.0
+
+### Minor Changes
+
+- Hygiene Module Cleanup and Filters
+
+## 1.5.1
+
+### Patch Changes
+
+- Add supply name field in display request items
+
+## 1.5.0
+
+### Minor Changes
+
+- Hygiene Schedule Task - Release
+
+## 1.4.0
+
+### Minor Changes
+
+- Hygiene Schedule Task - Initial Release
+
+## 1.3.0
+
+### Minor Changes
+
+- b90e31f: Update Modules - New features
+
+### Patch Changes
+
+- Updated dependencies [b90e31f]
+  - @iservice365/module-hygiene@1.3.0
+
+## 1.2.0
+
+### Minor Changes
+
+- 1170b7a: Hygiene Request Item - Release
+- d68da92: Hygiene Display Supply - Release
+
+## 1.1.0
+
+### Minor Changes
+
+- 0f65fa2: Hygiene Supply Stock and Request Item - Initial Release
+
+## 1.0.3
+
+### Patch Changes
+
+- fa485c3: Update dependencies
+- 3ac64f5: Fix export modules
+
+## 1.0.2
+
+### Patch Changes
+
+- 73be6af: Update dependencies
+
+## 1.0.1
+
+### Patch Changes
+
+- e7a734b: Update dependencies
+
+## 1.0.0
+
+### Major Changes
+
+- 05f4523: Initial release
+
+## 0.2.0
+
+### Minor Changes
+
+- 4a9a008: Add new dependencies
+
+## 0.1.2
+
+### Patch Changes
+
+- 6c38dd8: Dependencies - update
+
+## 0.1.1
+
+### Patch Changes
+
+- 41083ab: Dependencies - update
+
+## 0.1.0
+
+### Minor Changes
+
+- 7fe7aae: Cleaning check list - initial implementation
+
+## 0.0.1
+
+### Patch Changes
+
+- e03017c: init

package/PUBLISHING.md

@@ -0,0 +1,269 @@
+# Publishing Guide
+
+This document explains how to publish new versions of `@7365admin1/module-hygiene` to npm using changesets and GitHub Actions.
+
+## Overview
+
+The package uses an automated publishing workflow powered by [Changesets](https://github.com/changesets/changesets) and GitHub Actions. When you make changes and create a changeset, the workflow automatically:
+
+1. Creates a "Version Packages" PR with version bumps
+2. Publishes to npm when you merge that PR
+
+## Quick Start
+
+### 1. Make Your Changes
+
+Make your code changes in a new branch as usual.
+
+### 2. Create a Changeset
+
+Before committing, create a changeset to document your changes:
+
+```bash
+npx changeset
+```
+
+You'll be prompted to:
+- Select the type of change: `patch`, `minor`, or `major`
+- Write a summary of your changes
+
+This creates a `.changeset/[random-name].md` file.
+
+### 3. Commit and Push
+
+```bash
+git add .
+git commit -m "feat: your feature description"
+git push
+```
+
+### 4. Create a Pull Request
+
+Create a PR to merge your branch into `main`.
+
+### 5. Merge Your PR
+
+Once approved, merge your PR to `main`.
+
+### 6. Bot Creates Version PR (Automatic)
+
+After merging, the GitHub Actions bot will automatically:
+- Detect your changeset
+- Create a new PR titled "Version Packages"
+- Update `package.json` with the new version
+- Update `CHANGELOG.md`
+- Remove the changeset file
+
+### 7. Merge the Version PR
+
+Review and merge the "Version Packages" PR. This will:
+- Bump the version in `package.json`
+- Automatically publish to npm 🚀
+
+## Workflow Diagram
+
+```
+You: Make changes + create changeset
+         ↓
+You: Push and create PR
+         ↓
+You: Merge PR to main
+         ↓
+Bot: Creates "Version Packages" PR (automatic)
+         ↓
+You: Merge "Version Packages" PR
+         ↓
+Bot: Publishes to npm (automatic)
+```
+
+## Version Types
+
+When creating a changeset, you'll choose a version bump type:
+
+- **patch** (1.7.0 → 1.7.1): Bug fixes, minor changes
+- **minor** (1.7.0 → 1.8.0): New features, backward compatible
+- **major** (1.7.0 → 2.0.0): Breaking changes
+
+## Common Commands
+
+### Create a Changeset
+```bash
+npx changeset
+```
+
+### Create an Empty Changeset
+```bash
+npx changeset add --empty
+```
+
+### Check Which Packages Would Be Published
+```bash
+npx changeset status
+```
+
+### Manually Version (Local Testing Only)
+```bash
+npx changeset version
+```
+
+### Manually Publish (Not Recommended)
+```bash
+yarn run release
+```
+> ⚠️ **Note**: Manual publishing requires 2FA or an automation token. Use GitHub Actions instead.
+
+## GitHub Setup
+
+### Required Secrets
+
+The repository needs the following GitHub secret:
+
+**`NPM_TOKEN`**
+- Location: Settings → Secrets and variables → Actions
+- Type: Granular Access Token (Automation)
+- Value: Your npm automation token
+- Permissions: Read and Write for packages, with 2FA bypass enabled
+
+### Workflow Files
+
+- `.github/workflows/main.yml` - CI workflow (builds and tests)
+- `.github/workflows/publish.yml` - Publish workflow (creates PRs and publishes)
+
+## Configuration Files
+
+### `.changeset/config.json`
+
+```json
+{
+  "$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "access": "public",
+  "baseBranch": "main"
+}
+```
+
+Key settings:
+- `"access": "public"` - Package is published as public (free)
+- `"baseBranch": "main"` - PRs are created against main
+
+### `package.json`
+
+```json
+{
+  "name": "@7365admin1/module-hygiene",
+  "version": "1.7.0",
+  "author": "7365admin1",
+  "publishConfig": {
+    "access": "public"
+  }
+}
+```
+
+Key settings:
+- `"publishConfig.access": "public"` - Ensures scoped package is public
+
+## Troubleshooting
+
+### "Version didn't update on npm"
+
+**Solution**: Make sure you merged the bot's "Version Packages" PR. The version only publishes after merging that PR, not your original PR.
+
+### "No Version Packages PR was created"
+
+**Possible causes**:
+1. No changeset file was committed
+2. CI workflow failed
+3. Check GitHub Actions logs for errors
+
+**Solution**: Run `npx changeset status` locally to verify changesets exist.
+
+### "402 Payment Required" Error
+
+**Cause**: Scoped packages (`@username/package`) are private by default and require payment.
+
+**Solution**: Ensure `publishConfig.access` is set to `"public"` in `package.json`.
+
+### "403 Forbidden" or "401 Unauthorized"
+
+**Cause**: Invalid or expired npm token.
+
+**Solution**: 
+1. Generate a new Granular Access Token (Automation type) on npmjs.com
+2. Update the `NPM_TOKEN` secret in GitHub
+3. Ensure token has "Bypass 2FA" enabled
+
+### "Changeset not found" Error
+
+**Cause**: Changeset file wasn't committed or was deleted.
+
+**Solution**: Run `npx changeset` again and commit the generated `.changeset/*.md` file.
+
+## Best Practices
+
+### 1. Always Create Changesets
+
+Never merge code changes without a changeset. It ensures:
+- Version tracking
+- Changelog updates
+- Proper npm publishing
+
+### 2. Write Clear Changeset Summaries
+
+Your changeset summary becomes the changelog entry. Make it:
+- Clear and concise
+- User-focused (what changed, not how)
+- Action-oriented (e.g., "Added X feature" not "Adding X feature")
+
+### 3. Don't Skip the Version PR
+
+Always review and merge the "Version Packages" PR. It shows exactly what will be published.
+
+### 4. Use Yarn for Local Development
+
+The project uses Yarn for dependency management:
+
+```bash
+yarn install
+yarn build
+yarn lint
+```
+
+### 5. Keep `.npmrc` Private
+
+The `.npmrc` file contains your authentication token. It's in `.gitignore` - **never commit it!**
+
+## Security
+
+### npm Authentication
+
+- **GitHub Actions**: Uses `NPM_TOKEN` secret (automation token)
+- **Local Publishing**: Uses `.npmrc` file (not committed to git)
+
+### Token Types
+
+- **Automation tokens**: Bypass 2FA, designed for CI/CD
+- **Publish tokens**: Require 2FA, for manual publishing
+
+Always use automation tokens for GitHub Actions.
+
+## Package Information
+
+- **Name**: `@7365admin1/module-hygiene`
+- **Registry**: https://registry.npmjs.org/
+- **Package Page**: https://www.npmjs.com/package/@7365admin1/module-hygiene
+- **Author**: 7365admin1
+- **License**: MIT
+
+## Need Help?
+
+If you encounter issues:
+
+1. Check the [Changesets documentation](https://github.com/changesets/changesets)
+2. Review GitHub Actions workflow logs
+3. Verify npm token is valid and has correct permissions
+4. Ensure `.changeset/config.json` has `"access": "public"`
+
+---
+
+**Last Updated**: January 2026