@7365admin1/core 2.6.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,8 @@
1
+ # Changesets
2
+
3
+ Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
4
+ with multi-package repos, or single-package repos to help you version and publish your code. You can
5
+ find the full documentation for it [in our repository](https://github.com/changesets/changesets)
6
+
7
+ We have a quick list of common questions to get you started engaging with this project in
8
+ [our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)
@@ -0,0 +1,11 @@
1
+ {
2
+ "$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
3
+ "changelog": "@changesets/cli/changelog",
4
+ "commit": false,
5
+ "fixed": [],
6
+ "linked": [],
7
+ "access": "public",
8
+ "baseBranch": "main",
9
+ "updateInternalDependencies": "patch",
10
+ "ignore": []
11
+ }
@@ -0,0 +1,17 @@
1
+ name: CI
2
+ on:
3
+ push:
4
+ branches:
5
+ - "**"
6
+
7
+ jobs:
8
+ build:
9
+ runs-on: ubuntu-latest
10
+ steps:
11
+ - uses: actions/checkout@v4
12
+ - uses: actions/setup-node@v4
13
+ with:
14
+ node-version: 20.x
15
+ cache: "yarn"
16
+ - run: yarn install --frozen-lockfile
17
+ - run: yarn lint && yarn build
@@ -0,0 +1,39 @@
1
+ name: Publish
2
+ on:
3
+ workflow_run:
4
+ workflows: [CI]
5
+ branches: [main]
6
+ types: [completed]
7
+
8
+ concurrency: ${{ github.workflow }}-${{ github.ref }}
9
+
10
+ permissions:
11
+ contents: write
12
+ pull-requests: write
13
+
14
+ jobs:
15
+ publish:
16
+ if: ${{ github.event.workflow_run.conclusion == 'success' }}
17
+ runs-on: ubuntu-latest
18
+ steps:
19
+ - uses: actions/checkout@v4
20
+
21
+ - uses: actions/setup-node@v4
22
+ with:
23
+ node-version: 20.x
24
+ cache: "yarn" # Use yarn for caching
25
+ cache-dependency-path: yarn.lock # Cache Yarn lockfile
26
+
27
+ - run: yarn install --immutable # Install dependencies with immutable lockfile
28
+
29
+ - name: Create .npmrc for publishing
30
+ run: |
31
+ echo '//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}' > ~/.npmrc
32
+
33
+ - name: Create Release Pull Request or Publish
34
+ id: changesets
35
+ uses: changesets/action@v1
36
+ with:
37
+ publish: yarn release # Use yarn for publishing
38
+ env:
39
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
package/CHANGELOG.md ADDED
@@ -0,0 +1,255 @@
1
+ # @iservice365/core
2
+
3
+ ## 2.6.4
4
+
5
+ ### Patch Changes
6
+
7
+ - dfc78ee: Updated current features
8
+
9
+ ## 2.6.3
10
+
11
+ ### Patch Changes
12
+
13
+ - 984ed26: Revise CRON schedule for closing DOB
14
+ - eeaec60: Revise CRON for closing DOB
15
+ - 913798b: Revise CRON schedule for closing DOB
16
+
17
+ ## 2.6.2
18
+
19
+ ### Patch Changes
20
+
21
+ - ea82b60: Revise CRON for DOB
22
+
23
+ ## 2.6.1
24
+
25
+ ### Patch Changes
26
+
27
+ - 291f49a: Revised CRON - Bug fixes done
28
+
29
+ ## 2.6.0
30
+
31
+ ### Minor Changes
32
+
33
+ - 8c2ad2b: Daily Occurrence Book Management - CRON job and other related modules
34
+
35
+ ## 2.5.0
36
+
37
+ ### Minor Changes
38
+
39
+ - c0d1338: Update Modules - New Features
40
+
41
+ ## 2.4.0
42
+
43
+ ### Minor Changes
44
+
45
+ - 835c44b: Update Package - Update CRON job - New modules
46
+ - 7c9bab6: Daily Occurrence Book Managament - CRON job and other related features and modules
47
+
48
+ ## 2.3.1
49
+
50
+ ### Patch Changes
51
+
52
+ - c996d1e: Update package - New features
53
+
54
+ ## 2.3.0
55
+
56
+ ### Minor Changes
57
+
58
+ - a181da0: Multiple new modules - Release for core update
59
+
60
+ ## 2.2.7
61
+
62
+ ### Patch Changes
63
+
64
+ - 0d05442: Bulletin Board - Initial Release
65
+
66
+ ## 2.2.6
67
+
68
+ ### Patch Changes
69
+
70
+ - da037a2: Fix
71
+
72
+ ## 2.2.5
73
+
74
+ ### Patch Changes
75
+
76
+ - 4d3639c: Add service-provider-email to cookie
77
+
78
+ ## 2.2.4
79
+
80
+ ### Patch Changes
81
+
82
+ - 02d33ef: Use APP_ORG for service provider invite
83
+
84
+ ## 2.2.3
85
+
86
+ ### Patch Changes
87
+
88
+ - 5e8aed0: Fix getUserByEmail to case insensitive
89
+
90
+ ## 2.2.2
91
+
92
+ ### Patch Changes
93
+
94
+ - 2719f0f: Fix sign up service
95
+
96
+ ## 2.2.1
97
+
98
+ ### Patch Changes
99
+
100
+ - 0b80316: Facility management initial release
101
+
102
+ ## 2.2.0
103
+
104
+ ### Minor Changes
105
+
106
+ - b8c73b8: Virtual patrol initial release
107
+
108
+ ## 2.1.4
109
+
110
+ ### Patch Changes
111
+
112
+ - 2d7d3e4: Add new services
113
+
114
+ ## 2.1.3
115
+
116
+ ### Patch Changes
117
+
118
+ - ce1191d: Full session id migration
119
+
120
+ ## 2.1.2
121
+
122
+ ### Patch Changes
123
+
124
+ - 3a9d51e: Site camera - revise types
125
+
126
+ ## 2.1.1
127
+
128
+ ### Patch Changes
129
+
130
+ - 56b7f48: Dependencies - update
131
+
132
+ ## 2.1.0
133
+
134
+ ### Minor Changes
135
+
136
+ - c82fc6d: Customer sites - get by site id as service provider
137
+
138
+ ## 2.0.6
139
+
140
+ ### Patch Changes
141
+
142
+ - 0f71a0b: Service provider invitation - revision
143
+
144
+ ## 2.0.5
145
+
146
+ ### Patch Changes
147
+
148
+ - 1982d4a: User & Member mgmt - set default org on member verification
149
+
150
+ ## 2.0.4
151
+
152
+ ### Patch Changes
153
+
154
+ - 627ffb7: Fixed invite and member creation
155
+ - 0ad7aa1: Revision - adjust strictness for site name
156
+
157
+ ## 2.0.3
158
+
159
+ ### Patch Changes
160
+
161
+ - 2f13326: Revision - adjust add customer site service
162
+
163
+ ## 2.0.2
164
+
165
+ ### Patch Changes
166
+
167
+ - 3bab806: Revision - add app default role based on org nature
168
+
169
+ ## 2.0.1
170
+
171
+ ### Patch Changes
172
+
173
+ - 016af34: Revision - get site by name. Removed org option
174
+
175
+ ## 2.0.0
176
+
177
+ ### Major Changes
178
+
179
+ - 03687fa: Initial release
180
+
181
+ ## 1.0.0
182
+
183
+ ### Major Changes
184
+
185
+ - 321999c: Initial release
186
+
187
+ ### Patch Changes
188
+
189
+ - 9da798a: Vehicle mgmt - bypass delele on dahua error
190
+
191
+ ## 0.3.0
192
+
193
+ ### Minor Changes
194
+
195
+ - 1904a11: Vehicle mgmt - Initial release
196
+
197
+ ## 0.2.0
198
+
199
+ ### Minor Changes
200
+
201
+ - 1a63ba0: Dahua ANPR integration initial release
202
+
203
+ ## 0.1.3
204
+
205
+ ### Patch Changes
206
+
207
+ - 44384c6: Update dependencies
208
+
209
+ ## 0.1.2
210
+
211
+ ### Patch Changes
212
+
213
+ - 4fa908d: Building mgmt - update all unit building name
214
+
215
+ ## 0.1.1
216
+
217
+ ### Patch Changes
218
+
219
+ - 20e980a: Building mgmt - update building and unit details
220
+
221
+ ## 0.1.0
222
+
223
+ ### Minor Changes
224
+
225
+ - 8b88500: Building mgmt initial release
226
+
227
+ ## 0.0.5
228
+
229
+ ### Patch Changes
230
+
231
+ - 31b56e1: Update dependencies
232
+
233
+ ## 0.0.4
234
+
235
+ ### Patch Changes
236
+
237
+ - d5c15dd: Update dependencies
238
+
239
+ ## 0.0.3
240
+
241
+ ### Patch Changes
242
+
243
+ - f095047: Add sign up service
244
+
245
+ ## 0.0.2
246
+
247
+ ### Patch Changes
248
+
249
+ - 79e57e2: Fix handle user not found
250
+
251
+ ## 0.0.1
252
+
253
+ ### Patch Changes
254
+
255
+ - ca131b7: Init
package/PUBLISHING.md ADDED
@@ -0,0 +1,269 @@
1
+ # Publishing Guide
2
+
3
+ This document explains how to publish new versions of `@7365admin1/core` to npm using changesets and GitHub Actions.
4
+
5
+ ## Overview
6
+
7
+ 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:
8
+
9
+ 1. Creates a "Version Packages" PR with version bumps
10
+ 2. Publishes to npm when you merge that PR
11
+
12
+ ## Quick Start
13
+
14
+ ### 1. Make Your Changes
15
+
16
+ Make your code changes in a new branch as usual.
17
+
18
+ ### 2. Create a Changeset
19
+
20
+ Before committing, create a changeset to document your changes:
21
+
22
+ ```bash
23
+ npx changeset
24
+ ```
25
+
26
+ You'll be prompted to:
27
+ - Select the type of change: `patch`, `minor`, or `major`
28
+ - Write a summary of your changes
29
+
30
+ This creates a `.changeset/[random-name].md` file.
31
+
32
+ ### 3. Commit and Push
33
+
34
+ ```bash
35
+ git add .
36
+ git commit -m "feat: your feature description"
37
+ git push
38
+ ```
39
+
40
+ ### 4. Create a Pull Request
41
+
42
+ Create a PR to merge your branch into `main`.
43
+
44
+ ### 5. Merge Your PR
45
+
46
+ Once approved, merge your PR to `main`.
47
+
48
+ ### 6. Bot Creates Version PR (Automatic)
49
+
50
+ After merging, the GitHub Actions bot will automatically:
51
+ - Detect your changeset
52
+ - Create a new PR titled "Version Packages"
53
+ - Update `package.json` with the new version
54
+ - Update `CHANGELOG.md`
55
+ - Remove the changeset file
56
+
57
+ ### 7. Merge the Version PR
58
+
59
+ Review and merge the "Version Packages" PR. This will:
60
+ - Bump the version in `package.json`
61
+ - Automatically publish to npm 🚀
62
+
63
+ ## Workflow Diagram
64
+
65
+ ```
66
+ You: Make changes + create changeset
67
+
68
+ You: Push and create PR
69
+
70
+ You: Merge PR to main
71
+
72
+ Bot: Creates "Version Packages" PR (automatic)
73
+
74
+ You: Merge "Version Packages" PR
75
+
76
+ Bot: Publishes to npm (automatic)
77
+ ```
78
+
79
+ ## Version Types
80
+
81
+ When creating a changeset, you'll choose a version bump type:
82
+
83
+ - **patch** (2.6.4 → 2.6.5): Bug fixes, minor changes
84
+ - **minor** (2.6.4 → 2.7.0): New features, backward compatible
85
+ - **major** (2.6.4 → 3.0.0): Breaking changes
86
+
87
+ ## Common Commands
88
+
89
+ ### Create a Changeset
90
+ ```bash
91
+ npx changeset
92
+ ```
93
+
94
+ ### Create an Empty Changeset
95
+ ```bash
96
+ npx changeset add --empty
97
+ ```
98
+
99
+ ### Check Which Packages Would Be Published
100
+ ```bash
101
+ npx changeset status
102
+ ```
103
+
104
+ ### Manually Version (Local Testing Only)
105
+ ```bash
106
+ npx changeset version
107
+ ```
108
+
109
+ ### Manually Publish (Not Recommended)
110
+ ```bash
111
+ yarn run release
112
+ ```
113
+ > ⚠️ **Note**: Manual publishing requires 2FA or an automation token. Use GitHub Actions instead.
114
+
115
+ ## GitHub Setup
116
+
117
+ ### Required Secrets
118
+
119
+ The repository needs the following GitHub secret:
120
+
121
+ **`NPM_TOKEN`**
122
+ - Location: Settings → Secrets and variables → Actions
123
+ - Type: Granular Access Token (Automation)
124
+ - Value: Your npm automation token
125
+ - Permissions: Read and Write for packages, with 2FA bypass enabled
126
+
127
+ ### Workflow Files
128
+
129
+ - `.github/workflows/main.yml` - CI workflow (builds and tests)
130
+ - `.github/workflows/publish.yml` - Publish workflow (creates PRs and publishes)
131
+
132
+ ## Configuration Files
133
+
134
+ ### `.changeset/config.json`
135
+
136
+ ```json
137
+ {
138
+ "$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
139
+ "changelog": "@changesets/cli/changelog",
140
+ "commit": false,
141
+ "access": "public",
142
+ "baseBranch": "main"
143
+ }
144
+ ```
145
+
146
+ Key settings:
147
+ - `"access": "public"` - Package is published as public (free)
148
+ - `"baseBranch": "main"` - PRs are created against main
149
+
150
+ ### `package.json`
151
+
152
+ ```json
153
+ {
154
+ "name": "@7365admin1/core",
155
+ "version": "2.6.4",
156
+ "author": "7365admin1",
157
+ "publishConfig": {
158
+ "access": "public"
159
+ }
160
+ }
161
+ ```
162
+
163
+ Key settings:
164
+ - `"publishConfig.access": "public"` - Ensures scoped package is public
165
+
166
+ ## Troubleshooting
167
+
168
+ ### "Version didn't update on npm"
169
+
170
+ **Solution**: Make sure you merged the bot's "Version Packages" PR. The version only publishes after merging that PR, not your original PR.
171
+
172
+ ### "No Version Packages PR was created"
173
+
174
+ **Possible causes**:
175
+ 1. No changeset file was committed
176
+ 2. CI workflow failed
177
+ 3. Check GitHub Actions logs for errors
178
+
179
+ **Solution**: Run `npx changeset status` locally to verify changesets exist.
180
+
181
+ ### "402 Payment Required" Error
182
+
183
+ **Cause**: Scoped packages (`@username/package`) are private by default and require payment.
184
+
185
+ **Solution**: Ensure `publishConfig.access` is set to `"public"` in `package.json`.
186
+
187
+ ### "403 Forbidden" or "401 Unauthorized"
188
+
189
+ **Cause**: Invalid or expired npm token.
190
+
191
+ **Solution**:
192
+ 1. Generate a new Granular Access Token (Automation type) on npmjs.com
193
+ 2. Update the `NPM_TOKEN` secret in GitHub
194
+ 3. Ensure token has "Bypass 2FA" enabled
195
+
196
+ ### "Changeset not found" Error
197
+
198
+ **Cause**: Changeset file wasn't committed or was deleted.
199
+
200
+ **Solution**: Run `npx changeset` again and commit the generated `.changeset/*.md` file.
201
+
202
+ ## Best Practices
203
+
204
+ ### 1. Always Create Changesets
205
+
206
+ Never merge code changes without a changeset. It ensures:
207
+ - Version tracking
208
+ - Changelog updates
209
+ - Proper npm publishing
210
+
211
+ ### 2. Write Clear Changeset Summaries
212
+
213
+ Your changeset summary becomes the changelog entry. Make it:
214
+ - Clear and concise
215
+ - User-focused (what changed, not how)
216
+ - Action-oriented (e.g., "Added X feature" not "Adding X feature")
217
+
218
+ ### 3. Don't Skip the Version PR
219
+
220
+ Always review and merge the "Version Packages" PR. It shows exactly what will be published.
221
+
222
+ ### 4. Use Yarn for Local Development
223
+
224
+ The project uses Yarn for dependency management:
225
+
226
+ ```bash
227
+ yarn install
228
+ yarn build
229
+ yarn lint
230
+ ```
231
+
232
+ ### 5. Keep `.npmrc` Private
233
+
234
+ The `.npmrc` file contains your authentication token. It's in `.gitignore` - **never commit it!**
235
+
236
+ ## Security
237
+
238
+ ### npm Authentication
239
+
240
+ - **GitHub Actions**: Uses `NPM_TOKEN` secret (automation token)
241
+ - **Local Publishing**: Uses `.npmrc` file (not committed to git)
242
+
243
+ ### Token Types
244
+
245
+ - **Automation tokens**: Bypass 2FA, designed for CI/CD
246
+ - **Publish tokens**: Require 2FA, for manual publishing
247
+
248
+ Always use automation tokens for GitHub Actions.
249
+
250
+ ## Package Information
251
+
252
+ - **Name**: `@7365admin1/core`
253
+ - **Registry**: https://registry.npmjs.org/
254
+ - **Package Page**: https://www.npmjs.com/package/@7365admin1/core
255
+ - **Author**: 7365admin1
256
+ - **License**: MIT
257
+
258
+ ## Need Help?
259
+
260
+ If you encounter issues:
261
+
262
+ 1. Check the [Changesets documentation](https://github.com/changesets/changesets)
263
+ 2. Review GitHub Actions workflow logs
264
+ 3. Verify npm token is valid and has correct permissions
265
+ 4. Ensure `.changeset/config.json` has `"access": "public"`
266
+
267
+ ---
268
+
269
+ **Last Updated**: January 2026