Skip to content

Release 0.1.0 - #199

Merged
teo1747 merged 2 commits into
mainfrom
release-0.1.0
Nov 9, 2026
Merged

teo1747 merged 2 commits into
mainfrom
release-0.1.0

Conversation

@teo1747

@teo1747 teo1747 commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

Sets EMBCC_VERSION to 0.1.0, step 1 of Making a release. Once this is merged, the commit is tagged v0.1.0 and the release workflow builds and uploads the packages.

  • 0.1.0 has no suffix, so the workflow does not mark it a pre-release, GitHub makes it the latest release, and install.sh | sh installs it without --version. The README and the install page now say that; the examples of --version output and install paths say 0.1.0.
  • docs/releases/0.1.0.md: what changed since 0.0.1-beta (the host default target first, as the one change that can break a build).
  • The roadmap's 0.1.0 section says which exit criteria hold at the release. Since 2026-11-09 main requires the 17 ci checks to pass before a merge; what is still missing is three clean nightly runs in a row (2026-11-08 was the first).

Checked: embcc --version prints 0.1.0, make check 441/441, embdoc check 0 broken links (the notes page included).

The first release without a suffix, so GitHub makes it the latest one
and install.sh needs no --version. The README and the install page say
so; the examples print 0.1.0. docs/releases/0.1.0.md lists what changed
since 0.0.1-beta, and the roadmap says which of 0.1.0's exit criteria
hold: all but required checks on main.
Turned on for main on 2026-11-09: the 17 jobs of the ci workflow must
pass before a pull request merges. What 0.1.0 still lacks is three
clean nightly runs in a row.
@teo1747
teo1747 merged commit 5f98acc into main Nov 9, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant