Skip to content

Conversation

@jabraham17
Copy link
Contributor

@jabraham17 jabraham17 commented Dec 12, 2025

  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

!! This PR is currently a draft, using a release candidate tarball in a temporary location. On chapel 2.7 release day (dec 18) it will be replaced with the final release tarball in its permanent location, most likely the same tarball.

Update chapel URL and SHA for 2.7 release

Signed-off-by: Jade Abraham <[email protected]>
@github-actions github-actions bot added the python Python use is a significant feature of the PR or issue label Dec 12, 2025
@chenrui333 chenrui333 added the prerelease-testing Pull request from upstream, testing a pre-release with homebrew dependencies label Dec 12, 2025
@botantony botantony changed the title chapel 2.7 chapel 2.7.0 Dec 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

prerelease-testing Pull request from upstream, testing a pre-release with homebrew dependencies python Python use is a significant feature of the PR or issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants