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
Question 1: What is the problem?
The gemspec file does not specify the rackup version. The build seems to be failing with passenger-6.0.23. Can we have a rackup version specified in the gemspec file?
What is the expected behavior?
The build should be successful
What is the actual behavior?
Build is failing
How can we reproduce it?
Install passenger 6.0.23 gem without specifying rackup version. On my machine, it installs rackup 1.0.0 which is incompatible with this passenger version.
Question 2: Passenger version and integration mode:
Your answer: open source 6.0.23 standalone;
Question 3: OS or Linux distro, platform (including version):
Your answer: platform agnostic
Question 4: Passenger installation method:
Your answer:
RubyGems + Gemfile
RubyGems, no Gemfile
Phusion APT repo
Phusion YUM repo
OS X Homebrew
source tarball
Other, please specify:
Question 5: Your app's programming language (including any version managers) and framework (including versions):
Your answer: Ruby 3.3.1, Rails 7;
Question 6: Are you using a PaaS and/or containerization? If so which one?
Your answer: No
Question 7: Anything else about your setup that we should know?
Your answer: Install passenger 6.0.23 without specifying rackup version.
The text was updated successfully, but these errors were encountered:
I also wanted to briefly note: bumping rack to v3.0.0 for the passenger v6.0.23 patch release broke our deployments since it crossed two major release boundaries. I might recommend in the future making these kind of changes a minor release (at least).
Edit: let me clarify my breaking change comment. The rackup gem has a gemspec dependency of rack >= 3 for versions greater than v2.0.0. This means adding rackup as a dependency for the passenger v6.0.23 release transitively makes a hard requirement of rack >= 3. So even though passenger doesn't explicitly add the requirement of rack >= 3 in it's gemspec (it still specifies >= 1.6.13), any consumers of passenger will still be required to install rack >= 3.
Issue report
Question 1: What is the problem?
The gemspec file does not specify the rackup version. The build seems to be failing with passenger-6.0.23. Can we have a rackup version specified in the gemspec file?
What is the expected behavior?
The build should be successful
What is the actual behavior?
Build is failing
How can we reproduce it?
Install
passenger 6.0.23
gem without specifying rackup version. On my machine, it installsrackup 1.0.0
which is incompatible with this passenger version.Question 2: Passenger version and integration mode:
Your answer: open source 6.0.23 standalone;
Question 3: OS or Linux distro, platform (including version):
Your answer: platform agnostic
Question 4: Passenger installation method:
Your answer:
Question 5: Your app's programming language (including any version managers) and framework (including versions):
Your answer: Ruby 3.3.1, Rails 7;
Question 6: Are you using a PaaS and/or containerization? If so which one?
Your answer: No
Question 7: Anything else about your setup that we should know?
Your answer: Install
passenger 6.0.23
without specifyingrackup
version.The text was updated successfully, but these errors were encountered: