workflow-sandbox 0.3.0

Use environment variables for package name.

workflow-sandbox 0.2.0

This is the first release of workflow-sandbox using the release flow branching model/strategy. When a release candidate was identified (a574270, C below):

• A new branch maintenance/0.2.x was created, to service the minor release 0.2.
• The commit was tagged v0.2.0rc1, the first release candidate of this version.
• Using the release-branch-semver version scheme of pypa/setuptools-scm#430, subsequent untagged commits are versioned (with local scheme no-local-version):
  • On master as 0.3.0devN, e.g. 0.3.0dev1 (ee03672, E below);
  • On maintenance/0.2.x as 0.2.0rc2.dev1 (6006a6f, D below).
• In this example, the release candidate was deemed satisfactory and a dummy commit was used to create 6006a6f (F below) so that it could be uniquely tagged as v0.2.0.

In pictures, this looks like:

       D -- F [maintenance/0.2.x]
      /     ^ [v0.2.0]
B -- C---E [master]
     ^
[v0.2.0rc1]

Actual releases, e.g. 0.2.0 and bugfix releases 0.2.1, 0.2.2, etc. will be tagged on maintenance/0.2.x alone. This branch will contain no development, but cherry pick bug-fixes from master.

Note

• All tagged releases (including candidates) are published on PyPI and TestPyPI automatically.
• All untagged pushes to master and maintenance/* branches are published on TestPyPI automatically with a dev version.

workflow-sandbox 0.2.0rc1

This is the first release of workflow-sandbox using the release flow branching model/strategy. When a release candidate was identified (a574270, C below):

• A new branch maintenance/0.2.x was created, to service the minor release 0.2.
• The commit was tagged v0.2.0rc1, the first release candidate of this version.
• Using the release-branch-semver version scheme of pypa/setuptools-scm#430, subsequent untagged commits are versioned (with local scheme no-local-version):
  • On master as 0.3.0devN, e.g. 0.3.0dev1 (ee03672, E below);
  • On maintenance/0.2.x as 0.2.0rc2.dev1 (6006a6f, D below).

In pictures, this looks like:

       D [maintenance/0.2.x]
      /
B -- C---E [master]
     ^
[v0.2.0rc1]

Actual releases, e.g. 0.2.0 and bugfix releases 0.2.1, 0.2.2, etc. will be tagged on maintenance/0.2.x alone. This branch will contain no development, but cherry pick bug-fixes from master.

Note

• All tagged releases (including candidates) are published on PyPI and TestPyPI automatically.
• All pushes to master and maintenance/* branches are published on TestPyPI automatically with a dev version.

workflow-sandbox 0.1.4

v0.1.4

workflow-sandbox 0.1.3

v0.1.3

workflow-sandbox 0.1.2

v0.1.2

workflow-sandbox 0.1.0

First release of workflow-sandbox.