@myxtra/authentication-green 2.35.0-alpha.0 → 2.35.1-alpha.0
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 +0 -27
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -228,30 +228,3 @@ const onMessage = (message: MessageEvent<XtraAuthenticationMessageEventData>) =>
|
|
|
228
228
|
|
|
229
229
|
window.addEventListener('message', onMessage);
|
|
230
230
|
```
|
|
231
|
-
|
|
232
|
-
## Release Management
|
|
233
|
-
|
|
234
|
-
### Alpha to Production Promotion
|
|
235
|
-
|
|
236
|
-
To promote an alpha version to production after testing, use the following git commands:
|
|
237
|
-
|
|
238
|
-
```bash
|
|
239
|
-
# Create a promotion tag (replace version numbers with actual versions)
|
|
240
|
-
git tag promote-@myxtra/authentication-green@2.34.1-alpha.1-to-2.34.1
|
|
241
|
-
git push origin promote-@myxtra/authentication-green@2.34.1-alpha.1-to-2.34.1
|
|
242
|
-
```
|
|
243
|
-
|
|
244
|
-
This will trigger the Azure Pipeline to:
|
|
245
|
-
|
|
246
|
-
1. Download the tested alpha package
|
|
247
|
-
2. Remove the alpha suffix from the version
|
|
248
|
-
3. Republish as a production version with the `latest` tag
|
|
249
|
-
4. Clean up the alpha tag
|
|
250
|
-
|
|
251
|
-
**Tag Format:** `promote-<package-name>@<alpha-version>-to-<production-version>`
|
|
252
|
-
|
|
253
|
-
**Example:**
|
|
254
|
-
|
|
255
|
-
- Alpha version: `@myxtra/authentication-green@2.34.1-alpha.1`
|
|
256
|
-
- Production version: `@myxtra/authentication-green@2.34.1`
|
|
257
|
-
- Promotion tag: `promote-@myxtra/authentication-green@2.34.1-alpha.1-to-2.34.1`
|