CLAassistant
commented
6 years ago
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
dependabot-preview[bot]
Bumps releases from 1.4.0 to 1.4.1.
Changelog
*Sourced from releases's [changelog](https://github.com/bitprophet/releases/blob/master/docs/changelog.rst).* > ========= > Changelog > ========= > > * :release:`1.4.1 <2018-03-28>` > * :support:`73` Sphinx 1.7.x changed some semi-public APIs; given this is the > second minor release in a row to do so, we're explicitly bracketing our > ``setup.py`` dependencies to Sphinx >= 1.3 and < 1.7. We expect to bump this > up one minor release at a time as we add compatibility back in. > * :release:`1.4.0 <2017-10-20>` > * :support:`-` Drop Python 2.6 and 3.3 support, to correspond with earlier > changes in Sphinx and most other public Python projects. > * :bug:`- major` Identified a handful of issues with our Sphinx pin & > subsequently, internal changes in Sphinx 1.6 which broke (and/or appear to > break, such as noisy warnings) our own behavior. These have (hopefully) all > been fixed. > * :release:`1.3.2 <2017-10-19>` > * :support:`68 backported` Update packaging requirements to allow for > ``sphinx>=1.3,<2``. Thanks to William Minchin. > * :release:`1.3.1 <2017-05-18>` > * :bug:`60` Report extension version to Sphinx for improved Sphinx debug > output. Credit: William Minchin. > * :bug:`66` (via :issue:`67`) Deal with some Sphinx 1.6.1 brokenness causing > ``AttributeError`` by leveraging ``getattr()``'s default-value argument. > Thanks to Ian Cordasco for catch & patch. > * :release:`1.3.0 <2016-12-09>` > * :feature:`-` Add ``releases.util``, exposing (among other things) a highly > useful ``parse_changelog(path)`` function that returns a user-facing dict > representing a parsed changelog. Allows users to examine their changelogs > programmatically and answer questions like "do I have any outstanding bugs in > the 1.1 release line?". > * :release:`1.2.1 <2016-07-25>` > * :support:`51 backported` Modernize release management so PyPI trove > classifiers are more accurate, wheel archives are universal instead of Python > 2 only, and release artifacts are GPG signed. > * :bug:`56` Fix exceptions that occurred when no release/issue link options > were configured. Now those options are truly optional: release version and > issue number text will simply display normally instead of as hyperlinks. > Thanks to André Caron for the report. > * :bug:`36` Changelogs with no releases whatsoever should still be viable > instead of raising exceptions. This is now happily the case. All items in > such changelogs will end up in a single "unreleased features" list, just as > with regular prehistory entries. Thanks to Steve Ivy for initial report and > André Caron for additional feedback. > * :release:`1.2.0 <2016-05-20>` > * :bug:`- major` Fix formatting of release header dates; a "75% text size" > style rule has had an uncaught typo for some time. > * :bug:`55 major` Non-annotated changelog line items (which implicitly become > bugs) were incorrectly truncating their contents in some situations > (basically, any time they included non-regular-text elements like monospace, > ... (truncated)Commits
- [`aa4a794`](https://github.com/bitprophet/releases/commit/aa4a794086ed892305ce1fa862477c820a1f7430) Cut 1.4.1 - [`8276fa8`](https://github.com/bitprophet/releases/commit/8276fa81b7a64f08e0afa3651f7d1b921be1d556) Sphinx 1.7 broke some stuff, so let's make it explicit that we only support 1... - [`74371f7`](https://github.com/bitprophet/releases/commit/74371f78f496486bc414fee4db0fe5aa489e6d20) Bump to modern pypi.org compatible twine - [`783c651`](https://github.com/bitprophet/releases/commit/783c6513f16ec6b875a6af148cacb5aaae3ea3aa) Happy New Year - See full diff in [compare view](https://github.com/bitprophet/releases/compare/1.4.0...1.4.1)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot ignore this [minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use [this|these] label[s]` will set the current labels as the default for future PRs for this repo and language Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) Finally, you can contact us by mentioning @dependabot.