Skip to content

Releases: NangoHQ/nango

Data syncing

13 Jul 10:08
@bastienbeurier bastienbeurier
v0.24.5
1877cd3
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Data syncing

🚨 7 breaking changes (+ 4 self-hosted only)

1 - Global CLI installation (#740)

The Nango CLI should now be installed globally by running npm install nango -g (docs). Running CLI commands should no longer require npx or npm (e.g. nango generate instead of npx nango generate).

2 - Cloud-first developer experience (#760)

You no longer need to run Nango locally. In practice, you no longer have to run nango start and nango dev no longer runs Nango locally (simply watches and compiles your integrations files).

3 - Where to run CLI commands from (#760)

The Nango CLI commands should now be run from the ./nango-integrations folder (instead of one level above), except for the init command which creates the ./nango-integrations folder. As a result, your CLI .env file should be located inside the ./nango-integrations folder (instead of one level above).

4 - Environment keys (#760)

With the introduction of environments (dev and prod), you will now have multiple secret and public keys (cf. docs). The name of the corresponding environment variables has been changes to:

NANGO_SECRET_KEY_PROD='<prod-secret-key>'
NANGO_SECRET_KEY_DEV='<dev-secret-key>'

5 - CLI commands (#760)

CLI commands have changed (run nango to see the full list of commands), in particular:

  • sync:run|sr has become dryrun (arguments have changed)
  • deploy takes an additional "environement" argument (dev or prod)
  • unnecessary commands have been removed

6 - NANGO_HOSTPORT env var (#760)

By default the NANGO_HOSTPORT CLI env variable is no longer required (unless if you are using OSS).

7 - Deletes previous Activity logs (#734) & sync runs info

Due to changes in the DB schema for Activity logs & sync runs (introduced by dev environments), the Activity logs & sync runs schema migration would cause too much down time. As a result, Activity logs & sync runs previous to the migration will be dropped. The information about syncs might be missing for the time between the release and your next sync run.

Self-hosted 1 - Required public key (#760)

The Frontend SDK Nango constructor now requires a publicKey in all cases. You can find your automatically-generated public key in the dashboard's Project Settings (docs).

Self-hosted 2 - Required private key (#760)

The Backend Node SDK Nango constructor now requires a secretKey in all cases. You can find your automatically-generated secret key in the dashboard's Project Settings (docs).

Self-hosted 3 - No Basic auth (#760)

The OSS version no longer uses Basic auth. Similarly to cloud, It uses Bearer headers for authentication. This is handled for you if you use the Backend Node SDK and CLI. Changes are required if you use the REST API (docs).

Self-hosted 4 - .env settings moved to the dashboard

The callback URL & HMAC settings were moved from the env variables to the Nango dashboard (in the Project Settings tab). They are specific to a given environment (dev vs prod).

Other features in this release

Assets 2
Loading

v0.16.0 (Many improvements)

02 May 08:44
@bastienbeurier bastienbeurier
v0.16.0
ff364e8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.16.0 (Many improvements)

May 1, 2023

Hi everyone,

This weeks release (v0.16.0) comes with many improvements:

Bug fixes:

We are continuing to see a steady stream of amazing contributions, with a rapidly growing number of total contributors (now 75!). Thank you!!

Have a great week,

April 24, 2023

Hi everyone,

We have a LOT of improvements this week for version 0.15.0.

The main improvement is a way to make external API request with [Nango’s proxy](https://docs.nango.dev/reference/proxy)! It automatically handles authentication for you and will soon provide lots of other goodies (retries, monitoring, etc.).

Thanks you to @anand Chowdhary, @tony Xiao, @uncle-tee, @HarrisonJackson for your precious feedback, and most of all to @khaliq Gant for the implementation!

Another contributor has been killing it this week. [Chakravarthyyy](https://github.com/Chakravarthy7102) has made no less than 12 PRs this week, including many of super cool frontend improvements listed below. Thank you for jumping in like this!

Other improvements this week:

This was an amazing week, mostly thanks to the feedback and help of the community members here. We can’t thank you enough for this.

Have a great week,

April 17, 2023

Hi everyone,

Today we are release version 0.14.0, bringing the count to 96 integrations (hopefully 100+ next week 😎). These new integrations are:

In addition, we improved Nango’s reliability by adding [persistence storage for OAuth sessions](#426) (thank you @uncle-tee!)

Finally, we improved the onboarding by creating a default Github integration upon signing up to let you test an OAuth flow faster!

A huge shoutout for @uncle-tee who has been shipping integrations like crazy, as well as

Have a great week :)

April 11, 2023

Hi everyone,

Today we are releasing the version 0.13.4 and bring to total integration count to 88 with the following integrations:

We will continue to steadily increase the number of supported integrations. And don’t hesitate to request any specific one.

Have a great week!

April 3rd, 2023

Hi all!

We are excited to release 0.13.0 today with a bunch of new integrations:

Read more

Contributors

alan, robin, and 10 other contributors
Assets 2
Loading

v0.9.0 - Many improvements

03 Mar 10:12
@bastienbeurier bastienbeurier
v0.9.0
d078e93
Compare
Choose a tag to compare
v0.9.0 - Many improvements

It’s been a while since we officially released a new Nango version. But we have been hard at work and wanted to share the latest improvements coming with v0.9.0!
Unified Cloud lets you easily get started with Nango, without the hassle of self-hosting. We have seen that companies who use it build integrations faster. Get started with Nango Cloud for free.
55+ supported APIs including Brex, Stripe, Ramp, Confluence, Instagram, YouTube and many others.
Custom callback URL for Cloud makes Nango totally transparent for users, who now only see your domain while authorizing external providers.
Revamped frontend SDK using WebSocket (vs. window messages) which makes it much more robust and flexible.
1-click deployment with Heroku/Render and more detailed self-hosting documentation.
The biggest feature is coming soon: A dashboard where you can easily manage provider configurations & connections. This will also be the groundwork for many more improvements to the way you work with external APIs.

Assets 2
Loading

v0.3.6 - Full rewrite

30 Nov 13:53
@bastienbeurier bastienbeurier
v0.3.6
b4785e4
Compare
Choose a tag to compare
v0.3.6 - Full rewrite

We rewrote Pizzly to make the code more maintainable and accelerate future development.

It already works, and supports:

  • OAuth 1 & 2
  • a Docker container for the Pizzly server
  • a CLI to configure integrations
  • a Node SDK + REST API to fetch fresh tokens
  • a frontend SDK to initiate OAuth flows
Assets 2
Loading

v0.2.2

08 Jun 14:12
@cfabianski cfabianski
v0.2.2
d1d4c21
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.2.2 
Update Dockerfile
Assets 2
Loading