You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't verified whether there's a rationale behind it or if it's the default behavior when Fastlane creates a plugin, but I think it would be more appropriate to make it a public dependency.
I run into this in setting up a new project. I though it would have been enough to add the plugin to get access to Fastlane, but that wasn't the case. I found that inconvenient, because I now had to specify two gems instead of one.
The text was updated successfully, but these errors were encountered:
Currently,
fastlane
is a development dependency to this gem:release-toolkit/fastlane-plugin-wpmreleasetoolkit.gemspec
Line 54 in 4df4c38
I haven't verified whether there's a rationale behind it or if it's the default behavior when Fastlane creates a plugin, but I think it would be more appropriate to make it a public dependency.
I run into this in setting up a new project. I though it would have been enough to add the plugin to get access to Fastlane, but that wasn't the case. I found that inconvenient, because I now had to specify two gems instead of one.
The text was updated successfully, but these errors were encountered: