@equinor/fusion-framework-cli 12.3.10 → 12.4.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/CHANGELOG.md +57 -0
- package/bin/build/bin.mjs +1 -1
- package/bin/build/cli.mjs +3 -3
- package/dist/esm/version.js +1 -1
- package/dist/types/bin/index.d.ts +1 -1
- package/dist/types/bin/portal-tag.d.ts +3 -17
- package/dist/types/cli/commands/portal/publish.d.ts +1 -1
- package/dist/types/cli/commands/portal/tag.d.ts +1 -1
- package/dist/types/version.d.ts +1 -1
- package/docs/portal.md +7 -5
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,62 @@
|
|
|
1
1
|
# Change Log
|
|
2
2
|
|
|
3
|
+
## 12.4.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- [`393f163`](https://github.com/equinor/fusion-framework/commit/393f1637ed33b84a6330b5eb122ab549805416bd) Thanks [@Noggling](https://github.com/Noggling)! - **Portal Tags Now Support Any String Value**
|
|
8
|
+
|
|
9
|
+
Portal tagging functionality has been enhanced to accept any string value for tags instead of being restricted to predefined enum values.
|
|
10
|
+
|
|
11
|
+
**Breaking Changes**
|
|
12
|
+
|
|
13
|
+
- **Removed `AllowedPortalTags` enum**: The enum that previously restricted portal tags to only `'latest'` and `'preview'` has been removed.
|
|
14
|
+
- **No longer exported**: `AllowedPortalTags` is no longer exported from `@equinor/fusion-framework-cli/bin`.
|
|
15
|
+
|
|
16
|
+
**Migration**
|
|
17
|
+
|
|
18
|
+
If you were importing and using `AllowedPortalTags`:
|
|
19
|
+
|
|
20
|
+
```typescript
|
|
21
|
+
// Before
|
|
22
|
+
import { AllowedPortalTags } from '@equinor/fusion-framework-cli/bin';
|
|
23
|
+
await tagPortal({ tag: AllowedPortalTags.Latest, ... });
|
|
24
|
+
|
|
25
|
+
// After
|
|
26
|
+
await tagPortal({ tag: 'latest', ... });
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
**New Flexibility**
|
|
30
|
+
|
|
31
|
+
You can now use any string value for portal tags:
|
|
32
|
+
|
|
33
|
+
```bash
|
|
34
|
+
# Common tags still work
|
|
35
|
+
ffc portal publish --tag latest
|
|
36
|
+
ffc portal publish --tag preview
|
|
37
|
+
|
|
38
|
+
# New flexibility with custom tags
|
|
39
|
+
ffc portal publish --tag next
|
|
40
|
+
ffc portal publish --tag stable
|
|
41
|
+
ffc portal publish --tag v2.0.0-beta
|
|
42
|
+
ffc portal publish --tag release-candidate
|
|
43
|
+
ffc portal tag custom-environment --package my-portal@1.0.0
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
**Enhanced Documentation**
|
|
47
|
+
|
|
48
|
+
- Updated CLI help text with practical examples
|
|
49
|
+
- Added common tag examples (`latest`, `preview`, `next`, `stable`) in documentation
|
|
50
|
+
- Maintained guidance while showing flexibility
|
|
51
|
+
|
|
52
|
+
**Validation**
|
|
53
|
+
|
|
54
|
+
- Tags must be non-empty strings
|
|
55
|
+
- No other restrictions on tag format or content
|
|
56
|
+
- Backward compatibility maintained for existing tag values
|
|
57
|
+
|
|
58
|
+
This change provides much greater flexibility for deployment workflows while maintaining the same API structure and functionality.
|
|
59
|
+
|
|
3
60
|
## 12.3.10
|
|
4
61
|
|
|
5
62
|
### Patch Changes
|