CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

net/rubygem-google-cloud-env-gitlab 2.2.2

Provides information on Google Cloud Platform hosting environment

Maintainer
mfechner@FreeBSD.org
Packages
latest: 2.2.2
Upstream
up to date
Last update
to 2.2.2 · ef75f7041a
Quarterly
2026Q4: 2.2.2
WWW
https://github.com/googleapis/ruby-cloud-env
Links
cgit · VuXML

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 2.2.2.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (2)

Matthias Fechner (mfechner) · 2.2.2
net/rubygem-google-cloud-env-gitlab: update to 2.2.2

Changes:	https://github.com/googleapis/ruby-cloud-env/releases
ef75f7041a
Matthias Fechner (mfechner) · 2.2.1
www/gitlab: fix regression from 335fc7c38d61142727cb9f01fd9e401c476e4ad8

Gitlab requires net-http 0.4.1:
Because faraday >= 2, < 2.5 could not be found in locally installed gems
  and faraday >= 2.5, < 2.12.1 could not be found in locally installed gems,
  faraday >= 2, < 2.12.1 cannot be used.
And because faraday >= 2.12.1 depends on faraday-net_http >= 2.0, < 3.5,
  faraday >= 2 requires faraday-net_http >= 2.0, < 3.5.
Because faraday-net_http >= 3.4.0 depends on net-http >= 0.5.0
and faraday-net_http >= 2.0, < 3.4.0 could not be found in locally installed
gems,
  faraday-net_http >= 2.0 requires net-http >= 0.5.0.
Thus, faraday >= 2 requires net-http >= 0.5.0.
So, because Gemfile depends on faraday ~> 2
  and Gemfile depends on net-http = 0.4.1,
  version solving has failed.

While fixing the problem, moved gitlab used packages to own package names with a
PKGNAMESUFFIX of `-gitlab`.
This should make the gitlab package much more stable if updates in the ports are done.
edc8d0390e