openzeppelin-solidity - npm Package Compare versions

Comparing version 4.6.0 to 4.8.1

contracts/access/Ownable2Step.sol

contracts/interfaces/IERC2309.sol

contracts/interfaces/IERC4626.sol

contracts/token/ERC20/extensions/ERC4626.sol

contracts/token/ERC721/extensions/ERC721Consecutive.sol

contracts/token/ERC721/extensions/ERC721Votes.sol

contracts/utils/cryptography/EIP712.sol

contracts/vendor/arbitrum/IDelayedMessageProvider.sol

package.json

		{
		"name": "openzeppelin-solidity",
		"description": "Secure Smart Contract library for Solidity",
		"version": "4.6.0",
		"version": "4.8.1",
		"files": [
		@@ -16,4 +16,4 @@ "/contracts/*/.sol",
		"coverage": "env COVERAGE=true hardhat coverage",
		"docs": "oz-docs",
		"docs:watch": "npm run docs watch contracts 'docs/*.hbs' docs/helpers.js",
		"docs": "npm run prepare-docs && oz-docs",
		"docs:watch": "oz-docs watch contracts 'docs/templates' docs/config.js",
		"prepare-docs": "scripts/prepare-docs.sh",
		@@ -27,10 +27,12 @@ "lint": "npm run lint:js && npm run lint:sol",
		"clean": "hardhat clean && rimraf build contracts/build",
		"prepare": "npm run clean && env COMPILE_MODE=production npm run compile",
		"prepare": "scripts/prepare.sh",
		"prepack": "scripts/prepack.sh",
		"generate": "scripts/generate/run.js",
		"release": "scripts/release/release.sh",
		"version": "scripts/release/version.sh",
		"test": "hardhat test",
		"test:inheritance": "node scripts/inheritanceOrdering artifacts/build-info/*",
		"test:inheritance": "scripts/checks/inheritance-ordering.js artifacts/build-info/*",
		"test:generation": "scripts/checks/generation.sh",
		"gas-report": "env ENABLE_GAS_REPORT=true npm run test",
		"slither": "npm run clean && slither . --detect reentrancy-eth,reentrancy-no-eth,reentrancy-unlimited-gas --filter-paths contracts/mocks"
		"slither": "npm run clean && slither . --detect reentrancy-eth,reentrancy-no-eth,reentrancy-unlimited-gas"
		},
		@@ -56,5 +58,6 @@ "repository": {
		"devDependencies": {
		"@nomicfoundation/hardhat-network-helpers": "^1.0.3",
		"@nomiclabs/hardhat-truffle5": "^2.0.5",
		"@nomiclabs/hardhat-web3": "^2.0.0",
		"@openzeppelin/docs-utils": "^0.1.0",
		"@openzeppelin/docs-utils": "^0.1.3",
		"@openzeppelin/test-helpers": "^0.5.13",
		@@ -71,5 +74,7 @@ "chai": "^4.2.0",
		"ethereumjs-wallet": "^1.0.1",
		"glob": "^8.0.3",
		"graphlib": "^2.1.8",
		"hardhat": "^2.9.1",
		"hardhat-gas-reporter": "^1.0.4",
		"hardhat-ignore-warnings": "^0.2.0",
		"keccak256": "^1.0.2",
		@@ -86,4 +91,4 @@ "lodash.startcase": "^4.4.0",
		"solidity-ast": "^0.4.25",
		"solidity-coverage": "^0.7.18",
		"solidity-docgen": "^0.5.3",
		"solidity-coverage": "^0.8.0",
		"solidity-docgen": "^0.6.0-beta.29",
		"web3": "^1.3.0",
		@@ -90,0 +95,0 @@ "yargs": "^17.0.0"

README.md

		@@ -6,2 +6,3 @@ # <img src="logo.svg" alt="OpenZeppelin" height="40px">
		[![Coverage Status](https://codecov.io/gh/OpenZeppelin/openzeppelin-contracts/graph/badge.svg)](https://codecov.io/gh/OpenZeppelin/openzeppelin-contracts)
		[![gitpoap badge](https://public-api.gitpoap.io/v1/repo/OpenZeppelin/openzeppelin-contracts/badge)](https://www.gitpoap.io/gh/OpenZeppelin/openzeppelin-contracts)

		@@ -26,5 +27,5 @@ A library for secure smart contract development. Build on a solid foundation of community-vetted code.

		OpenZeppelin Contracts features a [stable API](https://docs.openzeppelin.com/contracts/releases-stability#api-stability), which means your contracts won't break unexpectedly when upgrading to a newer minor version.
		OpenZeppelin Contracts features a [stable API](https://docs.openzeppelin.com/contracts/releases-stability#api-stability), which means that your contracts won't break unexpectedly when upgrading to a newer minor version.

		An alternative to npm is to use the GitHub repository `openzeppelin/openzeppelin-contracts` to retrieve the contracts. When doing this, make sure to specify the tag for a release such as `v4.5.0`, instead of using the `master` branch.
		An alternative to npm is to use the GitHub repository (`openzeppelin/openzeppelin-contracts`) to retrieve the contracts. When doing this, make sure to specify the tag for a release such as `v4.5.0`, instead of using the `master` branch.

		@@ -48,7 +49,7 @@ ### Usage

		To keep your system secure, you should always use the installed code as-is, and neither copy-paste it from online sources, nor modify it yourself. The library is designed so that only the contracts and functions you use are deployed, so you don't need to worry about it needlessly increasing gas costs.
		To keep your system secure, you should always use the installed code as-is, and neither copy-paste it from online sources nor modify it yourself. The library is designed so that only the contracts and functions you use are deployed, so you don't need to worry about it needlessly increasing gas costs.

		## Learn More

		The guides in the [docs site](https://docs.openzeppelin.com/contracts) will teach about different concepts, and how to use the related contracts that OpenZeppelin Contracts provides:
		The guides in the [documentation site](https://docs.openzeppelin.com/contracts) will teach about different concepts, and how to use the related contracts that OpenZeppelin Contracts provides:

		@@ -58,7 +59,7 @@ * [Access Control](https://docs.openzeppelin.com/contracts/access-control): decide who can perform each of the actions on your system.
		* [Gas Station Network](https://docs.openzeppelin.com/contracts/gsn): let your users interact with your contracts without having to pay for gas themselves.
		* [Utilities](https://docs.openzeppelin.com/contracts/utilities): generic useful tools, including non-overflowing math, signature verification, and trustless paying systems.
		* [Utilities](https://docs.openzeppelin.com/contracts/utilities): generic useful tools including non-overflowing math, signature verification, and trustless paying systems.

		The [full API](https://docs.openzeppelin.com/contracts/api/token/ERC20) is also thoroughly documented, and serves as a great reference when developing your smart contract application. You can also ask for help or follow Contracts's development in the [community forum](https://forum.openzeppelin.com).

		Finally, you may want to take a look at the [guides on our blog](https://blog.openzeppelin.com/guides), which cover several common use cases and good practices.. The following articles provide great background reading, though please note, some of the referenced tools have changed as the tooling in the ecosystem continues to rapidly evolve.
		Finally, you may want to take a look at the [guides on our blog](https://blog.openzeppelin.com/guides), which cover several common use cases and good practices. The following articles provide great background reading, though please note that some of the referenced tools have changed, as the tooling in the ecosystem continues to rapidly evolve.

		@@ -65,0 +66,0 @@ * [The Hitchhiker’s Guide to Smart Contracts in Ethereum](https://blog.openzeppelin.com/the-hitchhikers-guide-to-smart-contracts-in-ethereum-848f08001f05) will help you get an overview of the various tools available for smart contract development, and help you set up your environment.

scripts/migrate-imports.js

		@@ -12,3 +12,3 @@ #!/usr/bin/env node
		'cryptography/MerkleProof.sol': 'utils/cryptography/MerkleProof.sol',
		'drafts/EIP712.sol': 'utils/cryptography/draft-EIP712.sol',
		'drafts/EIP712.sol': 'utils/cryptography/EIP712.sol',
		'drafts/ERC20Permit.sol': 'token/ERC20/extensions/draft-ERC20Permit.sol',
		@@ -15,0 +15,0 @@ 'drafts/IERC20Permit.sol': 'token/ERC20/extensions/draft-IERC20Permit.sol',

contracts/vendor/arbitrum/IMessageProvider.sol

contracts/access/AccessControl.sol