[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: avoid building and pushing custom images previous to the latest one

This happens for instance if we have released the 1.20.0 version but n8n publishes a 1.18.4 afterwards.

We are not interested in building that other image because we would prefer to wait for the fix applied to the 1.20.x branch

[email protected]

ci: unify new releases notification workflow due to GitHub restrictions

[email protected]

ci: only build custom image on new releases