@backstage/plugin-scaffolder-backend 1.1.0 → 1.2.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 +88 -0
- package/dist/index.cjs.js +473 -23
- package/dist/index.cjs.js.map +1 -1
- package/dist/index.d.ts +56 -1
- package/migrations/20220129100000_created_by.js +38 -0
- package/package.json +12 -12
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,93 @@
|
|
|
1
1
|
# @backstage/plugin-scaffolder-backend
|
|
2
2
|
|
|
3
|
+
## 1.2.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 9818112d12: Update the `github:publish` action to allow passing required status check
|
|
8
|
+
contexts before merging to the main branch.
|
|
9
|
+
- f8baf7df44: Added the ability to reference the user in the `template.yaml` manifest
|
|
10
|
+
- 8d5a2238a9: Split `publish:bitbucket` into `publish:bitbucketCloud` and `publish:bitbucketServer`.
|
|
11
|
+
|
|
12
|
+
In order to migrate from the deprecated action, you need to replace the use of action
|
|
13
|
+
`publish:bitbucket` in your templates with the use of either `publish:bitbucketCloud`
|
|
14
|
+
or `publish:bitbucketServer` - depending on which destination SCM provider you use.
|
|
15
|
+
|
|
16
|
+
Additionally, these actions will not utilize `integrations.bitbucket` anymore,
|
|
17
|
+
but `integrations.bitbucketCloud` or `integrations.bitbucketServer` respectively.
|
|
18
|
+
You may or may not have migrated to these already.
|
|
19
|
+
|
|
20
|
+
As described in a previous changeset, using these two replacement integrations configs
|
|
21
|
+
will not compromise use cases which still rely on `integrations.bitbucket` as this was
|
|
22
|
+
set up in a backwards compatible way.
|
|
23
|
+
|
|
24
|
+
Additionally, please mind that the option `enableLFS` is only available (and always was)
|
|
25
|
+
for Bitbucket Server use cases and therefore, is not even part of the schema for
|
|
26
|
+
`publish:bitbucketCloud` anymore.
|
|
27
|
+
|
|
28
|
+
### Patch Changes
|
|
29
|
+
|
|
30
|
+
- 0fc65cbf89: Override default commit message and author details in GitHub, Azure, bitbucket
|
|
31
|
+
- cfc0f19699: Updated dependency `fs-extra` to `10.1.0`.
|
|
32
|
+
- Updated dependencies
|
|
33
|
+
- @backstage/backend-common@0.13.3
|
|
34
|
+
- @backstage/plugin-catalog-backend@1.1.2
|
|
35
|
+
- @backstage/integration@1.2.0
|
|
36
|
+
- @backstage/plugin-scaffolder-common@1.1.0
|
|
37
|
+
- @backstage/config@1.0.1
|
|
38
|
+
- @backstage/catalog-client@1.0.2
|
|
39
|
+
- @backstage/catalog-model@1.0.2
|
|
40
|
+
|
|
41
|
+
## 1.2.0-next.1
|
|
42
|
+
|
|
43
|
+
### Minor Changes
|
|
44
|
+
|
|
45
|
+
- f8baf7df44: Added the ability to reference the user in the `template.yaml` manifest
|
|
46
|
+
|
|
47
|
+
### Patch Changes
|
|
48
|
+
|
|
49
|
+
- Updated dependencies
|
|
50
|
+
- @backstage/backend-common@0.13.3-next.2
|
|
51
|
+
- @backstage/plugin-catalog-backend@1.1.2-next.2
|
|
52
|
+
- @backstage/plugin-scaffolder-common@1.1.0-next.0
|
|
53
|
+
- @backstage/config@1.0.1-next.0
|
|
54
|
+
- @backstage/catalog-model@1.0.2-next.0
|
|
55
|
+
- @backstage/integration@1.2.0-next.1
|
|
56
|
+
- @backstage/catalog-client@1.0.2-next.0
|
|
57
|
+
|
|
58
|
+
## 1.2.0-next.0
|
|
59
|
+
|
|
60
|
+
### Minor Changes
|
|
61
|
+
|
|
62
|
+
- 9818112d12: Update the `github:publish` action to allow passing required status check
|
|
63
|
+
contexts before merging to the main branch.
|
|
64
|
+
- 8d5a2238a9: Split `publish:bitbucket` into `publish:bitbucketCloud` and `publish:bitbucketServer`.
|
|
65
|
+
|
|
66
|
+
In order to migrate from the deprecated action, you need to replace the use of action
|
|
67
|
+
`publish:bitbucket` in your templates with the use of either `publish:bitbucketCloud`
|
|
68
|
+
or `publish:bitbucketServer` - depending on which destination SCM provider you use.
|
|
69
|
+
|
|
70
|
+
Additionally, these actions will not utilize `integrations.bitbucket` anymore,
|
|
71
|
+
but `integrations.bitbucketCloud` or `integrations.bitbucketServer` respectively.
|
|
72
|
+
You may or may not have migrated to these already.
|
|
73
|
+
|
|
74
|
+
As described in a previous changeset, using these two replacement integrations configs
|
|
75
|
+
will not compromise use cases which still rely on `integrations.bitbucket` as this was
|
|
76
|
+
set up in a backwards compatible way.
|
|
77
|
+
|
|
78
|
+
Additionally, please mind that the option `enableLFS` is only available (and always was)
|
|
79
|
+
for Bitbucket Server use cases and therefore, is not even part of the schema for
|
|
80
|
+
`publish:bitbucketCloud` anymore.
|
|
81
|
+
|
|
82
|
+
### Patch Changes
|
|
83
|
+
|
|
84
|
+
- 0fc65cbf89: Override default commit message and author details in GitHub, Azure, bitbucket
|
|
85
|
+
- cfc0f19699: Updated dependency `fs-extra` to `10.1.0`.
|
|
86
|
+
- Updated dependencies
|
|
87
|
+
- @backstage/backend-common@0.13.3-next.0
|
|
88
|
+
- @backstage/integration@1.2.0-next.0
|
|
89
|
+
- @backstage/plugin-catalog-backend@1.1.2-next.0
|
|
90
|
+
|
|
3
91
|
## 1.1.0
|
|
4
92
|
|
|
5
93
|
### Minor Changes
|