Merging this PR to master will create a new version tag, perform the build release process, create a GitHub release and upload any assets created in the previous process to it.
PR back to dev branch will also be created afterwards.
Before merging this PR you can:
Review and discuss code changes of this PR.
Pull the created branch to local machine with: git pull origin/release/v0.5.0 and perform last-minute changes. Do not forget to commit and push.
After merging this PR to the master you HAVE to:
Delete release branch release/v0.5.0
Merge the second PR to the dev branch to retain release specific changes.
:clipboard: Changelog
Added
Command east build will now after every build step copy
, if found, from the build directory to the project
directory. This makes job of locating this file easier for clangd. Help
description for east build was updated to reflect that.
Changed
Make east.yml optional for everything, except for the usage of east build
command with --build-type option.
Make apps key and samples key inside east.yml optional. This is useful for
driver projects, which do not need apps, or any project that might not have
samples.
Fixed
Properly handle east build commands outside of applications and samples.
This means that running east build command will default to plain west
behaviour, as it should.
:robot::package: An automated release PR
This PR was created in response to a manual trigger of the
draft-new-release.yaml
workflow here: https://github.com/IRNAS/irnas-east-software/actions/runs/3684771243.The release workflow did the following things:
release/v0.5.0
branch,CHANGELOG.md
file,release/v0.5.0
branch to remote,:warning: Important notes
Merging this PR to
master
will create a new version tag, perform the build release process, create a GitHub release and upload any assets created in the previous process to it. PR back todev
branch will also be created afterwards.Before merging this PR you can:
git pull origin/release/v0.5.0
and perform last-minute changes. Do not forget to commit and push.After merging this PR to the
master
you HAVE to:release/v0.5.0
dev
branch to retain release specific changes.:clipboard: Changelog
Added
Changed
Fixed