All Versions
158
Latest Version
Avg Release Cycle
67 days
Latest Release
1252 days ago

Changelog History
Page 9

  • v0.24.0 Changes

    May 21, 2015

    ⬆️ How to upgrade

    If your code expects the estimated_minutes_watched or the average_view_duration report to return a Float, beware that they now return an Integer (since that is what YouTube returns). 📜 In case you still need to parse a float, just append .to_f to the result.

    • [ENHANCEMENT] Return Integer on estimated_minutes_watched reports
    • [ENHANCEMENT] Return Integer on average_view_duration reports
    • [FEATURE] New by: :referrer option for reports.
  • v0.23.2 Changes

    May 20, 2015
    • [FEATURE] Accept :includes in reports by video, related video and playlist to preload parts.
  • v0.23.1 Changes

    May 19, 2015
    • [FEATURE] New by: :month option for reports.
    • [FEATURE] New .reports method to fetch multiple metrics at once.
  • v0.23.0 Changes

    May 18, 2015

    ⬆️ How to upgrade

    If your code expects reports to return results by day then you must add 0️⃣ the by: :day option to your report method. The new default is by: :range. For instance channel.views would return

    {Wed, 8 May 2014 => 12.4, Thu, 9 May 2014 => 3.2, Fri, 10 May 2014 => …}
    

    and now returns the same as calling channel.views by: :range:

    {total: 3450}
    

    Additionally, if you expect reports by day then you must specify the :since option to your report method. Previously, this value was set to 0️⃣ 5.days.ago, but now is required. :until still defaults to Date.today.

    0️⃣ Finally, if you expect reports for the entire range, notice that the default :since option is now set to the date when YouTube opened. Therefore calling a method like channel.views now returns the lifetime views of a channel.

    • 0️⃣ [ENHANCEMENT] Change default from by: :day to by: :range.
    • [ENHANCEMENT] Require :since options for any report by day.
    • 0️⃣ [ENHANCEMENT] Change default range for reports by range to lifetime.
  • v0.22.2 Changes

    May 15, 2015
    • [FEATURE] New by: :search_term option for reports.
    • [FEATURE] New in: {state: 'XX'} option to limit reports to a US state
    • [FEATURE] New uniques by: :day report
  • v0.22.1 Changes

    May 13, 2015
    • [FEATURE] New by: :country option for channel, video and playlist reports
    • [FEATURE] New by: :state option for channel, video and playlist reports
    • [FEATURE] New :in option to limit reports to a country
  • v0.22.0 Changes

    April 30, 2015

    ⬆️ How to upgrade

    If your code expects any of the following method to return Float values, then be aware that they now return Integer. You can still call to_f if you do need a Float: views, comments, likes, dislikes, shares, subscribers_gained, subscribers_lost, favorites_added, favorites_removed, annotations, impressions, monetized_playbacks, playlist_starts.

    • [ENHANCEMENT] Return Integer values for reports that can never return decimal digits.
    • [FEATURE] New by: :range option for reports, to return a metric without dimensions (that is, for the whole range)
  • v0.21.0 Changes

    April 30, 2015

    ⬆️ How to upgrade

    If your code doesn’t use PolicyRule#ACTIONS, then you are good to go. If it does, then you should redefine the constant in your own app.

    • 🚚 [REMOVAL] Remove PolicyRule#ACTIONS (was %q(block monetize takedown track)).
    • 🛠 [BUGFIX] Make account.playlists and account.channel.playlists behave the same.
  • v0.20.0 Changes

    April 29, 2015

    ⬆️ How to upgrade

    If your code doesn’t use any of the following constants that were public but undocumented, then you are good to go.

    If it does, then you should redefine those constants in your own app, since it’s not Yt’s goal to validate the values posted to YouTube API.

    • 🚚 [REMOVAL] Remove Asset#STATUSES (was %q(active inactive pending)).
    • 🚚 [REMOVAL] Remove Claim#STATUSES (was %q(active appealed disputed inactive pending potential takedown unknown)).
    • 🚚 [REMOVAL] Remove Claim#CONTENT_TYPES (was %q(audio video audiovisual)).
    • 🖨 [REMOVAL] Remove Reference#STATUSES (was %q(activating active checking computing_fingerprint deleted duplicate_on_hold inactive live_streaming_processing urgent_reference_processing)).
    • 🚚 [REMOVAL] Remove Reference#CONTENT_TYPES (was %q(audio video audiovisual)).
    • 🚚 [REMOVAL] Remove Status#PRIVACY_STATUSES (was %q(private public unlisted)).
  • v0.19.0 Changes

    April 28, 2015

    ⬆️ How to upgrade

    If your code never calls partnered_channels.includes(:viewer_percentages) on a Yt::ContentOwner, then you are good to go.

    If it does, then be aware that viewer percentage is not eager-loaded anymore, so the call above is equivalent to partenered_channels. The reason is that viewer percentage requires a time-range, and using a default range of the last 3 months can generate more confusion than added value.

    🗄 Also if your code still uses the deprecated:

    • .viewer_percentages method, replace with .viewer_percentage.
    • ⚡️ policy.time_updated method, replace with policy.updated_at.
    • video.uploaded? method, replace with video.uploading?.

    • [REMOVAL] Remove .includes(:viewer_percentages) on content_owner.partnered_channels.

    • [REMOVAL] Remove deprecated viewer_percentages (use viewer_percentage instead)

    • ⚡️ [REMOVAL] Remove deprecated policy.time_updated (use updated_at instead)

    • 🚚 [REMOVAL] Remove deprecated video.uploaded? (use uploading? instead)