New script first detects what file is most recent, ie the most recent package to be added, then grabs it's source and attempts to clone the package. Then once the package is cloned it runs mason publish --ci-test which runs a series of compatibility checks to ensure that the package can be merged successfully with the mason-registry.
Right now this pulls the master branch of chapel as that's where the mason publish commands are, but should probably be set to the 1.20 release when possible.
New script first detects what file is most recent, ie the most recent package to be added, then grabs it's source and attempts to clone the package. Then once the package is cloned it runs
mason publish --ci-testwhich runs a series of compatibility checks to ensure that the package can be merged successfully with the mason-registry.Right now this pulls the master branch of chapel as that's where the
mason publishcommands are, but should probably be set to the 1.20 release when possible.As well as this PR relies on https://github.com/chapel-lang/chapel/pull/13938 being merged in order to work.