Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Prepare v0.7.4 release #28

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Prepare v0.7.4 release #28

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,18 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.7.4] (unreleased)
## [0.7.4] (2024.06.06)

### Added
- Added support for the `--application` (or `-a`) option to support AtomVM OTP applications.

### Fixed
- Fixed the `rebar3 new atomvm_app` template rebar.config file to use the provided app name for the start module.

### Changed

- Using the `-s init` option is still supported but deprecated. Use the `--application` (or `-a`) option to generate OTP applications using AtomVM.
- `pico_flash` task now uses picotool to reset the rp2040 device if a serial monitor is attached.

## [0.7.3] (2023.11.25)

Expand Down
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -401,15 +401,15 @@ You may use the `pico_flash` task to copy the generated AtomVM packbeam applicat
The `pico_flash` task depends on the `uf2create` task which in turn depends on `packbeam`, so in most cases it is not necessary to execute either of those tasks if the default settings are used, as any changes to modules in the project will get rebuilt before being flashed to the device.

shell$ rebar3 atomvm pico_flash
===> Fetching atomvm_rebar3_plugin v0.7.3
===> Fetching atomvm_rebar3_plugin v0.7.4
===> Fetching rebar3_hex v7.0.6
===> Fetching hex_core v0.8.4
===> Fetching verl v1.1.1
===> Analyzing applications...
===> Compiling hex_core
===> Compiling verl
===> Compiling rebar3_hex
===> Fetching atomvm_packbeam v0.6.0
===> Fetching atomvm_packbeam v0.7.3
===> Fetching rebar3_proper v0.12.1
===> Analyzing applications...
===> Compiling rebar3_proper
Expand Down Expand Up @@ -493,7 +493,7 @@ The `uf2create` task depends on the `packbeam` task, so the packbeam file will g
use the `version` task to print the current verison of the [`atomvm_rebar3_plugin`](https://atomvm.github.io/atomvm_rebar3_plugin) to the console.

shell$ rebar3 atomvm version
0.7.3
0.7.4

### The `bootstrap` task

Expand Down
2 changes: 1 addition & 1 deletion rebar.config
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{erl_opts, [debug_info]}.

{deps, [{atomvm_packbeam, "0.7.2"}]}.
{deps, [{atomvm_packbeam, "0.7.3"}]}.

{ex_doc, [
{source_url, <<"https://github.com/atomvm/atomvm_rebar3_plugin">>},
Expand Down
2 changes: 1 addition & 1 deletion src/atomvm_rebar3_plugin.app.src
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
%%
{application, atomvm_rebar3_plugin, [
{description, "A rebar plugin for manipulating AtomVM AVM files"},
{vsn, "0.7.3"},
{vsn, "0.7.4"},
{registered, []},
{applications, [kernel, stdlib]},
{env, []},
Expand Down
Loading