Skip to content

Releases: recurly/recurly-client-dotnet

1.4.14 (stable) / 2017-11-09

15 Nov 17:55
Compare
Choose a tag to compare
  • Fixed SSRF: replace EscapeUriString with EscapeDataString. Commit: 9eef460

1.3.2 (stable) / 2017-11-09

15 Nov 17:55
Compare
Choose a tag to compare
  • Fixed SSRF: replace EscapeUriString with EscapeDataString. Commit: 9eef460

1.2.8 (stable) / 2017-11-09

15 Nov 17:55
Compare
Choose a tag to compare
  • Fixed SSRF: replace EscapeUriString with EscapeDataString. Commit: 9eef460

1.1.10 (stable) / 2017-11-09

15 Nov 17:55
Compare
Choose a tag to compare
  • Fixed SSRF: replace EscapeUriString with EscapeDataString. Commit: 9eef460

1.0.1 (stable) / 2017-11-09

15 Nov 17:54
Compare
Choose a tag to compare
  • Fixed SSRF: replace EscapeUriString with EscapeDataString. Commit: 9eef460

1.8.0 (stable) / 2017-10-27

27 Oct 17:49
Compare
Choose a tag to compare
  • Adds giftcard redeem endpoint #250 (Issue #249)
  • Update the README with Overview section #251
  • Make TrialRequiresBillingInfo an optional #252
  • Implements missing revenue_schedule_type #253

Upgrade Notes

There is one small breaking change in this API version. TrialRequiresBillingInfo is now an optional so you will have to unwrap it to use it.

1.7.0 (stable) / 2017-10-18

18 Oct 15:33
Compare
Choose a tag to compare

This release will upgrade us to API version 2.8.

  • ImportedTrial flag on Subscription PR
  • Purchases Notes Changes PR

Upgrade Notes

There are two breaking changes in this API version you must consider.

Country Codes

All Country fields must now contain valid 2 letter ISO 3166 country codes. If your country code fails validation, you will receive a validation error. This affects any endpoint where an address is collected.

Purchase Currency

The purchases endpoint can create and invoice multiple adjustments at once but our invoices can only contain items in one currency. To make this explicit the currency can no longer be provided on an adjustment, it must be set once for the entire purchase:

// You must set the currency here
var purchase = new Purchase(accountCode, currency);

var adj = new Adjustment(4000, "HD Camera", 5);
// You can no longer set the currency on the adjustment level
adj.Currency = currency;
purchase.Adjustments.Add(adj);

1.6.1 (stable) / 2017-10-04

04 Oct 23:13
Compare
Choose a tag to compare
  • Fix Subscription#Postpone datetime format bug #244

1.6.0 (stable) / 2017-09-06

06 Sep 22:45
Compare
Choose a tag to compare

This bumps the library version to 1.6.0. A Nuget release and doc updates will follow.

  • Gift Card Support #241
  • Purchases Endpoint Support #240

Upgrade Notes

This release will upgrade us to API version 2.7. There is only 1 breaking change in this library.

Invoice will now use an enum for the CollectionMethod property instead of a string. The enum has 2 values (Automatic and Manual). Example:

// Setting
invoice.CollectionMethod = Invoice.Collection.Manual;

// Getting
if (invoice.CollectionMethod == Invoice.Collection.Automatic)
{
  // do something
}

1.5.0 (stable) / 2017-06-07

07 Jun 22:36
Compare
Choose a tag to compare

This brings us up to API v2.6

  • Added account balance endpoint #234 (issue #233)
  • Added plan and subscription changes #232
  • Fixing NullReferenceException in List() functions #231
  • Fixed a probable NRE in Plans.List() #230
  • Remove X-Records header #236

Upgrade Notes

This release will upgrade us to API version 2.6. There are two breaking changes related to this:

  1. To speed up your listing requests we’re no longer automatically computing the record counts for each requests. For our larger sites this could halve the response time. So in this release, we are removing the RecurlyList#Capacity method.
    to be cached for you. For more info see PR #324.
  2. For POST /v2/subscriptions Sending null for total_billing_cycles attribute will now override plan total_billing_cycles setting and will make subscription renew forever.
    Omitting the attribute will cause the setting to default to the value of plan total_billing_cycles.

There is a 3rd breaking change that was actually introduced in 1.4.5. The Account.Address property will no longer be pre-initialized so we no longer support this form. This will result in a NullReferenceException on the second line:

var account = new Account("asbcd123456");
account.Address.Address1 = "123 Canal St";
account.Address.City = "New Orleans";

The quick way to fix this is to initialize the address before setting its fields:

var account = new Account("asbcd123456");
account.Address = new Address(); // initialize Address first
account.Address.Address1 = "123 Canal St";
account.Address.City = "New Orleans";