0.5.2

Fix bug that prevented lock.json from being populated

After resolving version constraints, the correct revision was being determined but wasn't written to the lock.json file.

Fixed bug where corral update would result in incorrect code in the corral

When a dependency had a version constraint rather than a single value, the first time corral update was run, you wouldn't end up with the correct code checked out. The constraint was correctly solved, but the checked out code would be for branch main.

Make fetch an alias for update

When using version constraints rather than a specific revision, corral fetch would never set the repo to the correct state. Instead it would always leave the "version constraint using" dependency on the branch main.

The has been "fixed" by making fetch run the update command. It is possible that we will revisit this in the future and try to separate them. However, fixing is non-trivial and we felt it best to correct the glaring "doesn't work" error in corral fetch.

[0.5.2] - 2021-07-28

Fixed

• Fix bug that prevented lock.json from being populated (PR #193)
• Fixed bug where corral update would result in incorrect code in the corral (PR #194)
• Fixed bug where checked out code not matching revision (PR #198)

0.5.1

Switch supported FreeBSD to 13.0

As of this release, we now do all FreeBSD testing on FreeBSD 13.0 and all corral prebuilt packages are built on FreeBSD 13.0. We will make a best effort to not break prior versions of FreeBSD while they are "supported".

[0.5.1] - 2021-06-21

Changed

• Switch supported FreeBSD to 13.0 (PR #183)

0.5.0

Change "unknown branch" default to 'main'

GitHub has switched its default branch name from master to main for newly created repositories. Given this change, we expect that eventually most repositories will have their default branch named main, not master.

Corral will now use main and not master for the branch to use when using git or hg repos as a source.

Any corral.json dependency entries that aren't using a version should be updated to include master as the version to continue working as they did before or if you control the dependency, update its default branch to main and things will continue to work as before.

Switch support FreeBSD version

We've switched our supported FreeBSD from 12.1 to 12.2. The switch means that FreeBSD packages are tested and built on FreeBSD 12.2 and we no longer do any testing or building on 12.1.

You can continue using corral on FreeBSD 12.1 but we make no guarantees that it will work.

[0.5.0] - 2021-02-27

Changed

• Switch default branch to use when none is supplied to 'main` (PR #171)
• Switch supported FreeBSD to 12.2 (PR #173)

0.4.2

Add experimental packages field to corral.json

The addition of the packages field in an experimental fashion is the first step towards a bundle knowing, at a first class level, what packages it provides. The information will be used during documentation generation as well as for releasing bundles not as git/hg repos but as a compact format (like .tar.gz) that isn't the entire repo.

This field is subject to change and shouldn't be used by anyone who isn't currently a pony committer until such time as the features that rely on it are finalized.

[0.4.2] - 2021-02-07

Added

• Add new packages field to corral.json (PR #167)

0.4.1

Fix bundle scripts running during fetch of git repository

Corral was executing the bundle scripts while the git repository was being fetched. This was most noticable when downloading a bundle for the first time, as it was likely that the bundle file wasn't on disk when Corral tried to find the scripts to run.

The fix waits for the repository to be successfully fetched before executing the bundle scripts.

Don't remove empty optional fields from corral.json

Empty "info" object fields were previously removed from corral.json. This made it hard to know what additional information you should be providing as a library author.

Add documentation_url entry to bundle manifest

documentation_url will allow a forthcoming feature in the pony compiler to generate documentation for code that uses a given bundle to link to the documentation for that bundle from the code in question.

For example, ponylang/http will have its documentation link directly to the documentation for ponylang/regex and ponylang/net_ssl for types that come from those bundles.

[0.4.1] - 2021-01-28

Fixed

• Run PostFetchScript after fetch completion (PR #160)
• Don't remove empty fields from configuration (PR #164)

Added

• Add documentation_url to info section of corral.json (PR #166)

0.4.0

[0.4.0] - 2020-08-22

Added

• Add the ability to run a script after fetching or updating a dependency (PR #151)

Changed

• Make corral less verbose (PR #137)
• Update Dockerfile to use Alpine 3.12 (PR #153)
• Change status to beta (PR #154)

0.3.6

[0.3.6] - 2020-06-07

Fixed

• Remove extraneous CR in outputs on Windows (PR #115)
• Use correct path separator in PONYPATH on Windows (PR #117)
• Don't update dependencies more than once (PR #132)

0.3.5

[0.3.5] - 2020-05-13

Fixed

• Bug introduced in Pony runtime by ponyc 0.35.0

Changed

• Rename FreeBSD artifacts (PR #111)

0.3.4

[0.3.4] - 2020-05-10

Added

• Nothing. Fixing bad 0.3.2 release issue.

0.3.2

[0.3.2] - 2020-05-10

Added

• Add Windows Support (PR #83)
• Add FreeBSD support (PR #91)