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

Allow to overwrite the dev-repo field when creating a GH tag/release #494

Merged
merged 2 commits into from
Feb 3, 2025

Conversation

samoht
Copy link
Contributor

@samoht samoht commented Dec 13, 2024

This is useful for private projects where it's (sometimes) unclear what's the dev-repo field should look like (and sometimes dune will not generate the right one)

This is useful for private projects where it's (sometimes) unclear
what's the dev-repo field should look like.
@samoht samoht merged commit 6d9f26b into main Feb 3, 2025
3 checks passed
samoht added a commit to samoht/opam-repository that referenced this pull request Feb 3, 2025
CHANGES:

### Added

- Add `dune-release delegate-info version` to show the current version as infered
  by the tool (tarides/dune-release#495, @samoht)
- Add `--dev-repo` to `dune-release` and `dune-release publish` to overwrite
  the `dev-repo` field specified in the opam file (tarides/dune-release#494, @samoht)

### Changed

- Use the 'user' option as the fork owner, only attempt to decode the remote URL
  if the user option is not set. (tarides/dune-release#480, @Julow)

### Fixed

- Make `dune-release` not fail in the presence of `~/.dune/bin/dune` (which is present
  when using dune package management)

### Removed

- `dune-release` no longer publishes docs to github pages. Instead, we rely on
  the docs published under `ocaml.org/packages` (tarides/dune-release#499 tarides/dune-release#500, @v-gb @samoht)
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.

1 participant