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

Remove opam lint warnings for 1.2 files #2

Merged
merged 3 commits into from
Apr 13, 2018
Merged

Remove opam lint warnings for 1.2 files #2

merged 3 commits into from
Apr 13, 2018

Conversation

samoht
Copy link
Contributor

@samoht samoht commented Apr 13, 2018

No description provided.

@samoht samoht merged commit 74c5072 into master Apr 13, 2018
@samoht samoht deleted the lint branch April 13, 2018 08:13
samoht added a commit to samoht/opam-repository that referenced this pull request Jun 8, 2018
CHANGES:

- Remove opam lint warnings for 1.2 files (tarides/dune-release#2, @samoht)
- Add a `--keep-v` option to not drop `v` at the beginning of version
  numbers (tarides/dune-release#6, @samoht)
- Pass `-p <package>` to jbuilder (tarides/dune-release#8, @diml)
- Fix a bug in `Distrib.write_subst` which could cause an infinite loop
  (tarides/dune-release#10, @diml)
- Add a `--dry-run` option to avoid side-effects for all commands (@samoht)
- Rewrite issues numbers in changelog to point to the right repository
  (tarides/dune-release#13, @samoht)
- Stop force pushing tags to `origin`. Instead, just force push the release
  tag directly to the `dev-repo` repository (@samoht)
- Fix publishing distribution when the the tag to publish is not the repository
  HEAD (tarides/dune-release#4, @samoht)
- Do not depend on `opam-publish` anymore. Use configuration files stored
  in `~/.dune` to parametrise the publishing workflow. (@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