Skip to content

Support uploading/displaying changelogs. #160

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

Closed
huonw opened this issue Jun 9, 2015 · 3 comments
Closed

Support uploading/displaying changelogs. #160

huonw opened this issue Jun 9, 2015 · 3 comments
Labels
C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works

Comments

@huonw
Copy link
Member

huonw commented Jun 9, 2015

I'm not sure what this would look like, but it would be useful to be able to see what's changed.

(I could also imagine a cargo diff foo 1.0.3 1.3.2 that downloads/displays the changelogs between those versions.)

@lukaslueg
Copy link
Contributor

I would much prefer to have a changelog in Cargo.toml, which is then parsed by cargo or rendered by crates.io

@carols10cents carols10cents added the C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works label Dec 15, 2016
@ruuda
Copy link

ruuda commented Jun 26, 2017

Here’s a suggestion for a small change that could help a lot: add a changelog field to the crate metadata, similar to homepage, repository and documentation. Crates.io would include a link to the changelog under the “Links” section, similar to the other fields.

People could link it to a changelog.md file in a repository browser such as GitHub, or to a dedicated page on a project site.

As a user of a crate (as opposed to when I am still deciding on whether to use a crate), the two things for which I most often visit a crate page are the docs and the changelog. A direct link could save a click and page load (assuming the changelog is linked from the repository page).

@carols10cents
Copy link
Member

Discussion of this should now happen on RFC 2129, and if that is accepted, it'll get its own tracking issue, so I'm going to close this one.

bors added a commit that referenced this issue Dec 17, 2019
…ent-shim-3.7.1, r=locks

Bump ember-cli-moment-shim from 3.5.0 to 3.7.1

Bumps [ember-cli-moment-shim](https://github.com/jasonmit/ember-cli-moment-shim) from 3.5.0 to 3.7.1.
<details>
<summary>Commits</summary>

- [`0dca3a1`](jasonmit/ember-cli-moment-shim@0dca3a1) 3.7.1
- [`d2bba3b`](jasonmit/ember-cli-moment-shim@d2bba3b) Revert "Support including moment locales as a single module. ([#158](https://github-redirect.dependabot.com/jasonmit/ember-cli-moment-shim/issues/158))"
- [`7fcd915`](jasonmit/ember-cli-moment-shim@7fcd915) 3.7.0
- [`61ce1a5`](jasonmit/ember-cli-moment-shim@61ce1a5) Updating lockfile
- [`c3f7da5`](jasonmit/ember-cli-moment-shim@c3f7da5) Remove deprecated dependency exists-sync ([#160](https://github-redirect.dependabot.com/jasonmit/ember-cli-moment-shim/issues/160))
- [`efa6e5d`](jasonmit/ember-cli-moment-shim@efa6e5d) Update README.md
- [`b0e09a6`](jasonmit/ember-cli-moment-shim@b0e09a6) Support including moment locales as a single module. ([#158](https://github-redirect.dependabot.com/jasonmit/ember-cli-moment-shim/issues/158))
- [`dfb8214`](jasonmit/ember-cli-moment-shim@dfb8214) Linting
- [`d2103d4`](jasonmit/ember-cli-moment-shim@d2103d4) 3.6.0
- [`7604274`](jasonmit/ember-cli-moment-shim@7604274) Upgrading dependencies
- Additional commits viewable in [compare view](jasonmit/ember-cli-moment-shim@v3.5.0...v3.7.1)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=ember-cli-moment-shim&package-manager=npm_and_yarn&previous-version=3.5.0&new-version=3.7.1)](https://dependabot.com/compatibility-score.html?dependency-name=ember-cli-moment-shim&package-manager=npm_and_yarn&previous-version=3.5.0&new-version=3.7.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-automerge-start)
[//]: # (dependabot-automerge-end)

---

**Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com).

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor 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 these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

</details>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works
Projects
None yet
Development

No branches or pull requests

4 participants