object-assign versions and release history

Inspect a published release before upgrading or adding a dependency. Each version reference keeps its metadata and provider measurements pinned to that exact npm version.

Published versions17
Stable versions17
Prereleases0
Releases published in the last 90 days0
Deprecated releases0
Latest npm dist-tag4.1.1

All available releases

VersionPublishedRuntime dependenciesTypesStatus
4.1.12017-01-16T15:35:15.282Z0Not declaredlatest
4.1.02016-05-02T18:09:55.804Z0Not declared
4.0.12015-08-20T12:34:04.010Z0Not declared
4.0.02015-08-20T09:06:05.735Z0Not declared
2.1.12015-06-05T14:26:28.479Z0Not declared
3.0.02015-06-04T14:09:02.051Z0Not declared
2.0.02014-11-22T03:40:09.589Z0Not declared
1.0.02014-08-14T10:45:03.502Z0Not declared
0.4.02014-08-13T07:47:00.902Z0Not declared
0.3.12014-04-30T22:36:40.407Z0Not declared
0.3.02014-04-11T22:34:55.461Z0Not declared
0.2.22014-04-08T13:53:46.644Z0Not declared
0.2.12014-03-24T14:06:35.136Z0Not declared
0.2.02014-02-15T21:39:23.178Z0Not declared
0.1.22014-02-04T21:03:17.088Z0Not declared
0.1.12014-02-04T20:02:13.757Z0Not declared
0.1.02014-02-02T15:47:58.857Z0Not declared

Choosing a version

The latest tag is selected by the publisher and is not a guarantee of compatibility. Prerelease and deprecated status remain visible. Check your Node.js range and peer requirements on the exact version page, then review the maintainer’s release notes before upgrading.

Removed or unpublished versions may be absent. Historical download charts cover all package versions and do not show adoption of an individual release.

npm release-history source — retrieved 2026-10-29T08:40:34.013Z