@imfusion/web-ui 0.5.1-dev.38.g1e36ac04 → 0.5.1-dev.40.gfb5bc73e
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/README.md
CHANGED
|
@@ -143,7 +143,7 @@ namespace.
|
|
|
143
143
|
|
|
144
144
|
Release-facing changes are recorded as one-line entries in [`CHANGELOG.md`](./CHANGELOG.md) under `## [Unreleased]`. The
|
|
145
145
|
commit workflow requires an entry for pull-request commits and direct commits to `master`, with only narrow mechanical
|
|
146
|
-
exceptions.
|
|
146
|
+
exceptions. Each entry ends with its author as ` — Name <email>`, taken from the committer's git config.
|
|
147
147
|
|
|
148
148
|
The published version is derived from git tags, not from `package.json`.
|
|
149
149
|
|
package/package.json
CHANGED
|
@@ -134,6 +134,10 @@ verification again, and show a second report with the migration paths, held-back
|
|
|
134
134
|
If no findings exist, report that the installed update has no detected compatibility fixes, changed usages, or replacement
|
|
135
135
|
candidates. Do not create an empty migration commit.
|
|
136
136
|
|
|
137
|
+
Whatever the migration outcome, close the phase by asking whether to run `imf-web-ui-audit full`: an update can shift the
|
|
138
|
+
baseline (new components, hooks, conventions), and the audit report shows where the project now stands against it. Run it
|
|
139
|
+
only on an explicit yes.
|
|
140
|
+
|
|
137
141
|
## Migration approval
|
|
138
142
|
|
|
139
143
|
Ask exactly, **“Approve these consumer migration changes and commit them separately?”** Do not commit without an affirmative
|