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

Release 1.4.0 into develop #292

Merged
merged 10 commits into from
Aug 4, 2021
Merged

Release 1.4.0 into develop #292

merged 10 commits into from
Aug 4, 2021

Conversation

AliSoftware
Copy link
Contributor

New version 1.4.0

@AliSoftware AliSoftware added the Releases Release related stuff label Aug 2, 2021
@AliSoftware AliSoftware requested a review from a team August 2, 2021 13:52
@AliSoftware AliSoftware self-assigned this Aug 2, 2021
@mokagio
Copy link
Contributor

mokagio commented Aug 3, 2021

Just a note here on the failing GitHub Actions build because:

Unable to find a spec satisfying nokogiri (~> 1.11) in the set. Perhaps the
lockfile is corrupted? Found nokogiri (1.11.7-x86_64-darwin) that did not match
the current platform.

I need to learn more about how Bundler 2.2.x manages the platforms, but I think we can work around this by adding the following to .bundle/config:

BUNDLE_SPECIFIC_PLATFORM: "false"

(We could also ignore this and move on, but isn't it unsatisfying?)

@mokagio mokagio mentioned this pull request Aug 3, 2021
mokagio added a commit that referenced this pull request Aug 4, 2021
See discussion here: #292 (comment)

To ensure the setting is persisted for every user of the repository, I
decided to track the Bundler config file. This seems like a good idea
anyway, even though Bundler currently has a bug resulting in that file
being changed sometimes, which can be confusing for developers.

See rubygems/rubygems#3708
See discussion here: #292 (comment)

To ensure the setting is persisted for every user of the repository, I
decided to track the Bundler config file. This seems like a good idea
anyway, even though Bundler currently has a bug resulting in that file
being changed sometimes, which can be confusing for developers.

See rubygems/rubygems#3708
We don't need them because we don't run the tests in that workflow.
There is no "screenshots" group. That option didn't produce any effect.
@mokagio
Copy link
Contributor

mokagio commented Aug 4, 2021

Opened #293 to address the CI issue.

Copy link
Contributor

@mokagio mokagio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Once #293 gets into the release branch, we should be able to merge and ship.

@codecov-commenter
Copy link

Codecov Report

Merging #292 (1308134) into develop (ebe98e8) will increase coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #292      +/-   ##
===========================================
+ Coverage    51.62%   51.64%   +0.02%     
===========================================
  Files          108      108              
  Lines         4533     4533              
===========================================
+ Hits          2340     2341       +1     
+ Misses        2193     2192       -1     
Impacted Files Coverage Δ
...mreleasetoolkit/helper/promo_screenshots_helper.rb 22.09% <0.00%> (+0.55%) ⬆️

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 ebe98e8...1308134. Read the comment docs.

@AliSoftware AliSoftware merged commit e02e57d into develop Aug 4, 2021
@AliSoftware AliSoftware deleted the release/1.4.0 branch August 4, 2021 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Releases Release related stuff
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants