onflow/flow-core-contracts

Use semantic versioning and tags

Closed this issue · 3 comments

Problem

ATM this repo is not tagged when used in things like flowkit

Steps to Reproduce

Nothing

Acceptance Criteria

When this repo is used in a tagged version of upstream code it should use a tag from this repo

Context

Working on dependent code that is not updated correctly because commit versions are used and not tags.

before/while we're at it, let's also tag a new version for https://github.com/onflow/flow-ft

and update this import to use the tag:

github.com/onflow/flow-ft/lib/go/contracts v0.7.1-0.20230711213910-baad011d2b13

I tagged new versions for flow-nft and flow-ft after merging the feature branches. I'm working on getting the tests passing here after upgrading the dependencies, and then I'll do a release here.

I just published the new releases for flow-core-contracts