@linked365/pptb-mockaroo-data-munger 1.0.1 → 1.0.3
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.
- package/IMPLEMENTATION.md +8 -0
- package/npm-shrinkwrap.json +2 -2
- package/package.json +2 -2
package/IMPLEMENTATION.md
CHANGED
|
@@ -35,6 +35,14 @@ Commands:
|
|
|
35
35
|
- `npm run build` — type-check and create the production bundle.
|
|
36
36
|
- `npx pptb-validate` — validate the package manifest and distribution metadata.
|
|
37
37
|
|
|
38
|
+
## Release automation
|
|
39
|
+
|
|
40
|
+
The release workflow uses manifest-driven Release Please configuration in `release-please-config.json` and `.release-please-manifest.json`. The manifest starts from the existing package version, 1.0.2, rather than the older v0.4.2 GitHub release. Conventional commits determine the next version (for example, a fix produces 1.0.3); there is no permanent forced release version.
|
|
41
|
+
|
|
42
|
+
The bootstrap SHA marks the main-branch commit where the package was already 1.0.2, preventing old release history from being included in the initial migration changelog. Release Please ignores this boundary after a matching release exists.
|
|
43
|
+
|
|
44
|
+
Merge these configuration changes into `main`, then run the Release workflow or let its push trigger run. Review the generated 1.x release PR instead of manually editing its package version. Release Please maintains the manifest, package metadata, shrinkwrap, and changelog in its release PR. Root-package release outputs continue to drive the existing tag checkout and npm publish job.
|
|
45
|
+
|
|
38
46
|
## Manual testing checklist
|
|
39
47
|
|
|
40
48
|
Run these checks inside Power Platform ToolBox against a disposable development or sandbox Dataverse environment, not production. Use synthetic data, check for plug-ins or flows triggered by record creation, and plan cleanup: the tool has no automatic rollback. Leave items unchecked until a person has verified the result; automated tests and screenshots alone do not complete this checklist.
|
package/npm-shrinkwrap.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@linked365/pptb-mockaroo-data-munger",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.3",
|
|
4
4
|
"lockfileVersion": 3,
|
|
5
5
|
"requires": true,
|
|
6
6
|
"packages": {
|
|
7
7
|
"": {
|
|
8
8
|
"name": "@linked365/pptb-mockaroo-data-munger",
|
|
9
|
-
"version": "1.0.
|
|
9
|
+
"version": "1.0.3",
|
|
10
10
|
"license": "MIT",
|
|
11
11
|
"dependencies": {
|
|
12
12
|
"@fluentui/react-components": "^9.72.8",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@linked365/pptb-mockaroo-data-munger",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.3",
|
|
4
4
|
"displayName": "Mockaroo Data Munger",
|
|
5
5
|
"description": "A tool to mock data from Mockaroo into your Dataverse tables",
|
|
6
6
|
"main": "index.html",
|
|
@@ -31,7 +31,7 @@
|
|
|
31
31
|
"configurations": {
|
|
32
32
|
"repository": "https://github.com/LinkeD365/Mockaroo-DataMunger",
|
|
33
33
|
"website": "https://linked365.blog",
|
|
34
|
-
"readmeUrl": "https://raw.githubusercontent.com/LinkeD365/Mockaroo-DataMunger/refs/heads/
|
|
34
|
+
"readmeUrl": "https://raw.githubusercontent.com/LinkeD365/Mockaroo-DataMunger/refs/heads/main/README.md"
|
|
35
35
|
},
|
|
36
36
|
"repository": {
|
|
37
37
|
"type": "git",
|