chapel-lang / mason-registry Goto Github PK

Hi there,

I'm happy to have finally submitted my first library to mason, hopefully not the last one and happy to be the guinea pig to smooth the workflow edges :)

One question, the documentation instructions don't mention to manually create a tag when using mason publish, as such I assumed this would be done automatically, but it does not seem the case (repo link).

Do I need to make the release manually? Or should that be handled by mason publish ?

You can close this one after review.

The mason registry didn't get the memo about renaming master to main. This change might need to be coordinated with a Chapel release if the master branch is explicitly referred to from within the mason codebase.

Update README for mason-registry to reflect mason publish workflow that allows for one to publish a package to the registry.

SParks would be do delighted he'd burst into the sky! I'll make popcorn!

Go ahead, ask Ben A! I'll watch, it'll be awesome.

We ought to implement a small travis test to:

• verify the source location exists
• verify the TOML file:
  • is valid TOML
  • contains the required information

The cache.toml file to be used in mason-registry after merge of #48 uses TOML table headers as [LocalAtomics."0.1.0"] which is invalid as per parsing by our Chapel's TOML module. This may be updated to [LocalAtomics.0.1.0] or [LocalAtomics0.1.0].