Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
Cabal
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Contributor analytics
CI/CD analytics
Repository analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Haskell
Cabal
Commits
8bde3a6f
Unverified
Commit
8bde3a6f
authored
11 months ago
by
mergify[bot]
Committed by
GitHub
11 months ago
Browse files
Options
Downloads
Plain Diff
Merge pull request #9946 from cabalism/docs/user-visible-is
Define a user-visible change
parents
41c140a4
c0ba5531
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+9
-3
9 additions, 3 deletions
CONTRIBUTING.md
with
9 additions
and
3 deletions
CONTRIBUTING.md
+
9
−
3
View file @
8bde3a6f
...
...
@@ -290,9 +290,15 @@ issues) when appropriate.
Changelog
---------
When opening a pull request with a user-visible change, you should write one changelog entry
(or more in case of multiple independent changes) — the information will end up in
our release notes.
Anything that changes
`cabal-install:exe:cabal`
or changes exports from library
modules or changes behaviour of functions exported from packages published to
hackage is a
<a
id=
"user-visible-change"
>
user-visible change
</a>
. Raising the
lower bound on
`base`
is most definitely a user-visible change because it
excludes versions of GHC from being able to build these packages.
When opening a pull request with a user-visible change, you should write one
changelog entry (or more in case of multiple independent changes) — the
information will end up in our release notes.
Changelogs for the next release are stored in the
`changelog.d`
directory.
The files follow a simple key-value format similar to the one for
`.cabal`
files.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment