@backstage/plugin-scaffolder-backend 1.1.0-next.2 → 1.2.0-next.1

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