You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of relying on QEMU emulation to build multi-arch images, use
native arm64 and amd64 build runners to build architecture-specific
images, then publish multi-arch metadata with each of the image
manifests.
Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
**Note:** A docker image with a matching V.R version is required before releasing a new version of Fabric.
11
11
@@ -17,10 +17,12 @@ The following tasks are required before releasing:
17
17
18
18
- Update version numbers in `build.gradle` files to the required version
19
19
- Update test, sample, and docs files to match the new version
20
-
- Update the [`COMPATIBILITY.md`](./COMPATIBILITY.md)
20
+
- Update the [`COMPATIBILITY.md`](./COMPATIBILITY.md)
21
21
22
22
See the [[FABCJ-289] release: 2.2.0 LTS](https://github.com/hyperledger/fabric-chaincode-java/pull/124) pull request for an example, although be careful to search for all versions in the codebase as they're easy to miss and things change!
23
23
24
+
Ensure the last branch build passed since exactly this repository state will be released.
25
+
24
26
## Create release
25
27
26
28
Creating a GitHub release on the [releases page](https://github.com/hyperledger/fabric-chaincode-java/releases) will trigger the build to publish the new release.
@@ -57,6 +59,7 @@ See the [Bump version to 2.2.1](https://github.com/hyperledger/fabric-chaincode-
57
59
## Interim Build Publishing
58
60
59
61
The nightly Azure Pipeline Builds will also publish the 'dev' drivers to Artifactory. These can be accessed via the repository at
0 commit comments