chore(deps): update semantic-release to version ^24.2.0

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417

[babblebey]

This pull request updates the package.json file to upgrade the semantic-release package in attempt to bump the semantic-release/github plugin to v11.0.1

Other Changes Made

• Removed semantic-release from peerDependencies; happened follwoing the uninstallation action to bump the semantic-release version; just thought to keep it that since the devDeps of semantic-release isn't pinned to a certain version anymore with the hope of returning that when beta merges to master

[travi]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those. secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking. also, small nit-pick: try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

[babblebey]

a few things to consider with this. this change needs to be in the beta branch, not master. once the other changes in the beta branch get promoted, this sort of change can come along with those.

Well noted, I just thought the change might not work immediately for the release at the point of merging... I still think we will be using the version v11.0.0 of semantic-release/github that point of merging beta to master. Good to know its alright though.

secondly, there should be no need to remove the peer dependencies definition. that is there for consumers and we need to be careful with changes to that since most changes there should be considered breaking.

True, that is! I will revert this an see what peer version best suites

try to make sure that the devDependency remains pinned rather than defined as a range. if installing with the npm cli, the -E or --save-exact flag would accomplish this.

✍️

[babblebey]

Now closing this in favour of #417