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

www/rubygem-faraday-gitlab 2.14.3

HTTP/REST API client library in Ruby

Port info

Maintainer
mfechner@FreeBSD.org
Packages
latest: 2.14.3
Upstream
up to date
Last update
to 2.14.3 · 4369e8b337
Quarterly
2026Q4: 2.14.3
WWW
https://github.com/lostisland/faraday
Links
cgit · VuXML

Install

Package
# pkg install rubygem-faraday-gitlab
installs 2.14.3 from latest; from quarterly (2026Q4) 2.14.3
Port
# cd /usr/ports/www/rubygem-faraday-gitlab && make install clean
Size
67 KiB download · 312 KiB installed
Depends on
devel/ruby-gems 4.0.21, devel/rubygem-json 3.0.2, devel/rubygem-logger-gitlab 1.7.0, lang/ruby34 3.4.9_2,1, www/rubygem-faraday-net_http-gitlab 3.3.0_1
License
MIT

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 162.14.32.14.3–
FreeBSD 152.14.32.14.3–
FreeBSD 142.14.32.14.32.14.3

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 152.14.32.14.3–
FreeBSD 142.14.32.14.32.14.3

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

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

Fixed (0)

No VuXML entries for this package.

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

None.

Commits (9)

Matthias Fechner (mfechner) · 2.14.3 MFH 2026Q3 ✓
www/rubygem-faraday-gitlab: update to 2.14.3

Required for gitlab 19.2.0

Changes:	https://github.com/lostisland/faraday/releases
4369e8b337
Matthias Fechner (mfechner) · 2.14.2
www/rubygem-faraday-gitlab: update to 2.14.2

Required for gitlab 19.1.0

Changes:	https://github.com/lostisland/faraday/releases
cb5b930a06
Matthias Fechner (mfechner) · 2.13.4_2
www/gitlab: fix deps caused by intermediate commits
957a409f77
Matthias Fechner (mfechner) · 2.13.4_1
www/rubygem-faraday-gitlab: fixed conflict in 2025Q4 with rubygem-json
7a33398708
Matthias Fechner (mfechner) · 2.13.4
www/rubygem-faraday-gitlab: update to 2.13.4

Changes:	https://github.com/lostisland/faraday/releases
8d201eadd9
Matthias Fechner (mfechner) · 2.13.1
www/rubygem-faraday-gitlab: update to 2.13.1

Required for gitlab 18.1

Changes:	https://github.com/lostisland/faraday/releases/tag/v2.13.1
aa41fb4c02
Matthias Fechner (mfechner) · 2.12.2
www/gitlab: fix rubygem-logger conflict
c7aedd6f91
Matthias Fechner (mfechner) · 2.12.2
www/rubygem-faraday-gitlab: update to 2.12.2

Changes:	https://github.com/lostisland/faraday/releases/tag/v2.12.2
2d93403799
Matthias Fechner (mfechner) · 2.12.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