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

Start using semver branches. #129

Closed
wants to merge 1 commit into from
Closed

Start using semver branches. #129

wants to merge 1 commit into from

Conversation

rosiel
Copy link
Member

@rosiel rosiel commented Oct 5, 2021

GitHub Issue: Islandora/documentation#1907

What does this Pull Request do?

Milliner, Recast, Hypercube and Homarus use semver in their composer.json files. I regenerated their composer.lock files as well. (though, see Islandora/documentation#1908)

This pull request does NOT touch the composer requirements for Houdini, which still uses the dev-symfony-flex branch of crayfish commons.

@codecov
Copy link

codecov bot commented Oct 5, 2021

Codecov Report

Merging #129 (836074d) into 2.x (0a54c76) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##                2.x     #129   +/-   ##
=========================================
  Coverage     77.55%   77.55%           
  Complexity      159      159           
=========================================
  Files             6        6           
  Lines           655      655           
=========================================
  Hits            508      508           
  Misses          147      147           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0a54c76...836074d. Read the comment docs.

@seth-shaw-unlv
Copy link
Contributor

Let's get a response to Islandora/documentation#1908 during the Tech Call tomorrow before we proceed with this one.

@rosiel
Copy link
Member Author

rosiel commented Oct 6, 2021

Update from the Committers' call:

Updating the lock file to all new versions is probably a good thing to do every once in a while, but should not be merged without actually testing!

During the call, @jordandukart suggested a better way with cleaner diffs. I'll close this PR and make a new one.

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.

2 participants