Skip to content

Conversation

gigorok
Copy link
Contributor

@gigorok gigorok commented Dec 16, 2020

closes #1343

related rails commits:
rails/rails@b0cc7d9
rails/rails@b30a23f

All Submissions:

  • I've checked to ensure there aren't other open Pull Requests for the same update/change.
  • I've submitted a ticket for my issue if one did not already exist.
  • My submission passes all tests. (Please run the full test suite locally to cut down on noise from travis failures.)
  • I've used Github auto-closing keywords in the commit message or the description.
  • I've added/updated tests for this change.

New Feature Submissions:

  • I've submitted an issue that describes this feature, and received the go ahead from the maintainers.
  • My submission includes new tests.
  • My submission maintains compliance with JSON:API.

Bug fixes and Changes to Core Features:

  • I've included an explanation of what the changes do and why I'd like you to include them.
  • I've provided test(s) that fails without the change.

Test Plan:

Reviewer Checklist:

  • Maintains compliance with JSON:API
  • Adequate test coverage exists to prevent regressions

@gigorok gigorok changed the base branch from master to release-0-9 December 16, 2020 08:07
@gigorok gigorok force-pushed the rails-6-1 branch 2 times, most recently from 72bc1ff to d9f77e0 Compare December 16, 2020 11:41
@gigorok gigorok marked this pull request as ready for review December 16, 2020 13:33
Copy link

@marcelolx marcelolx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good for me

@marcelolx
Copy link

@lgebhardt Could you take a look on this?

@rsmithlal
Copy link

How are things going with this PR? I just ran into this issue reported in #1343 today while trying to upgrade my engine using jsonapi-resources to 6.1. Do you need a hand with something? If I can help move this issue along and get a new release version published, please let me know.

has_many :comments
has_and_belongs_to_many :tags, join_table: :posts_tags
has_many :special_post_tags, source: :tag
has_many :special_post_tags
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was this failing on 6.1?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep. because of rails/rails@b30a23f

@nadnoslen
Copy link

Hey @bf4 & @lgebhardt & @marcelolx!

Hope you guys are well. Thanks again for all your work on this project.

I was looking at this PR the other day. This appears to be the bare minimum to permit Rails-6.1 compliance for the 0.9 version stream. Any hope that we get this blessed and released in the coming days?

Thanks for putting this PR together @gigorok

@lgebhardt lgebhardt merged commit ad64f14 into cerebris:release-0-9 Jan 18, 2021
lgebhardt pushed a commit that referenced this pull request Jan 19, 2021
@lgebhardt lgebhardt mentioned this pull request Jan 19, 2021
12 tasks
lgebhardt added a commit that referenced this pull request Jan 20, 2021
* Rails v6.1 compatibility (#1346)

* Fixes for rails 6.1.1

* Fixes for ruby 3.0.0

* Remove rails 5.0 support

Co-authored-by: Igor Gonchar <[email protected]>
@qrush
Copy link

qrush commented Jan 25, 2021

Checking in here as I'm upgrading an app to Rails 6.1 - is there any chance a gem could be cut for 0.9.x? 🙏

lgebhardt added a commit that referenced this pull request Feb 4, 2021
* Rails v6.1 compatibility (#1346)

* Fixes for rails 6.1.1

* Fixes for ruby 3.0.0

* Remove rails 5.0 support

Co-authored-by: Igor Gonchar <[email protected]>

(cherry picked from commit 1322b59)
lgebhardt added a commit that referenced this pull request Feb 4, 2021
* Setup github actions for CI

(cherry picked from commit e894827)

* Rails 6.1 (#1352)

* Rails v6.1 compatibility (#1346)

* Fixes for rails 6.1.1

* Fixes for ruby 3.0.0

* Remove rails 5.0 support

Co-authored-by: Igor Gonchar <[email protected]>

(cherry picked from commit 1322b59)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants