Bug 1975977

Summary: rubygem-rails-6.1.4 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: rubygem-railsAssignee: mo
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mo, mtasaka, pvalena, ruby-packagers-sig, sseago, s, strzibny, tdawson, vondruch
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-rails-6.1.4-1.fc35 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-21 13:23:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Upstream Release Monitoring 2021-06-24 20:45:16 UTC
Latest upstream release: 6.1.4
Current version/release in rawhide: 6.1.3.2-1.fc35
URL: http://rubyonrails.org

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/4305/

Comment 1 Upstream Release Monitoring 2021-06-24 20:45:21 UTC
Unable to resolve the hostname for one of the package's Source URLs

Comment 2 Fedora Update System 2021-07-21 13:23:55 UTC
FEDORA-2021-9e230f5209 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.