Comments (4)
This is not possible right now, but I'm not sure why it's necessary at all.
If I run composer install
and get my/package
v1.0.0, that version is written to the lock file. Anyone else that does a composer install
with that lock file gets that version of the module. If I run composer update my/package
and get 1.1.0 and my patch no longer applies, at that point, I'm going to have to re-patch the module (whether that's by re-rolling the patch or not having the patch anymore or whatever). When you update your module, just update your patch.
Am I missing something?
from composer-patches.
No, you are absolutely right! Thanks!
from composer-patches.
I've got a specific case where I can't think of an alternative. I've a module that needs a patch to core. All is good for 8.3.x. That patch has been committed to 8.4.x, which is not yet released, but I want to be able to run my tests against it so I can be prepared if anything changes or breaks.
from composer-patches.
Tere is fork vaimo/composer-patches, which allow patch up to a specific version.
from composer-patches.
Related Issues (20)
- Clear error-message if patch is not available HOT 3
- COMPOSER environment variable vs patches.lock HOT 6
- `PatchesFile` resolver should use the Composer downloader to open the patches file HOT 2
- Redirect loop in documentation pages - Github says to go to docs.cweagans.net/composer-patches - that page says the documentation is in README.md on Github... HOT 2
- Add option to allow composer to continue if patches don't apply HOT 4
- New documentation website is missing the ignore-patches HOT 1
- Should not uninstall packages when Composer is called with --no-install HOT 2
- [Bug or new feature] Add support for local patch files and external patch file in dependencies HOT 10
- Clear error-message if patch is not available HOT 7
- How to apply patches from URL to a private GitHub repo? HOT 2
- PHP 8.2 support HOT 7
- SIMPLE example HOT 1
- When installing Drupal module metatag version: '8.x-1.19' module, the sub module metatag_extended_perms gets created twice, once inside a folder named b HOT 5
- The patch is partially applied HOT 3
- [2.0.0-beta1] No available patcher was able to apply patch ( for drupal/core ) HOT 7
- Composer require hangs sometimes when a patch applies HOT 2
- Removing package for re-install and re-patch does not trigger if patches definition is empty (1.7.3) HOT 1
- I'm Confused By Some of the Directions HOT 5
- [2.*] Make lock file path configurable HOT 2
- Write copy of a patch to a project directory for code review HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from composer-patches.