Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CHaP & hackage indices #544

Merged
merged 1 commit into from
May 28, 2024
Merged

Conversation

carbolymer
Copy link
Contributor

Changelog

- description: |
    Update CHaP & hackage indices
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
   - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

Bumping hackage & chap prior to bumping hedgehog-extras downstream, to make sure we're building fine.

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated. See Running tests for more details
  • Self-reviewed the diff

@carbolymer carbolymer force-pushed the mgalazyn/chore/bump-chap-hackage branch 2 times, most recently from c3edd0d to e757c1d Compare May 27, 2024 12:33
@carbolymer carbolymer enabled auto-merge May 27, 2024 13:29
@carbolymer carbolymer disabled auto-merge May 27, 2024 13:30
@carbolymer carbolymer force-pushed the mgalazyn/chore/bump-chap-hackage branch from e757c1d to 2aa523e Compare May 28, 2024 06:46
@carbolymer carbolymer merged commit f1531bc into main May 28, 2024
18 of 19 checks passed
@carbolymer carbolymer deleted the mgalazyn/chore/bump-chap-hackage branch May 28, 2024 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants