-
### Summary
The NPM module does not consider version if you use `state: present`. For example, if I need to install `npm @^7.0.0`, then the presence of npm 6.14.2 satisfies this module. However, it s…
-
Should fix the following comment from #49:- https://github.com/pwsh-cs-tools/core/issues/49#issuecomment-1898185715
> +1, sharing the temp path causes errors if two packages contain the same file e…
-
This is to track the path to releasing a version 1.0 of this gem. The gem is currently fully functional and usable. The benefits of releasing a 1.0 are largely practical in that it gives more room for…
-
Beside Dompdf I did not work on any snake_case project in the last years. Even worse are the classes mixing both notations like CPdf and the adapter or files which are mainly camelCase like options.
…
-
The new [packages](
https://www.w3.org/TR/xslt-30/#packages-and-modules) feature allows us to have better encapsulation and a clearer API definition (which makes for better documentation and allows u…
-
1. Rename the project from **SWFObject** to **SWFObject3**
reasons:
- too many CDN, repositories, package managers, etc. use the name `swfobject`
see for example [swfobject on npmjs](ht…
-
As we are using semantic versioning it is critical to understand the nature of the changes when creating releases. For example, if the release branch has some commits on it which have not been release…
-
Create version tags and create a stable C API interface that follows semantic versioning (https://semver.org/). A C API will make it easy to create bindings from other languages and allow for changes …
-
@masterbee I saw from 2c2d058 that release 4.1 is now planned, that is great.
What would be the difference between 4.0.x vs 4.1.x?
Are we going to use [semantic versioning](http://semver.org/) n…
-
### Bug Description
Some commands, like clean, should not need such a strict schema validation, if all they gonna do is “clean”. IoW, if I want to `clean` my project, the YAML shouldn't have an imp…