Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency jwilder/nginx-proxy to v1 #149

Merged
merged 1 commit into from
Jun 20, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2022

Mend Renovate

This PR contains the following updates:

Package Update Change
jwilder/nginx-proxy major 0.9.0 -> 1.0.1

Release Notes

nginx-proxy/nginx-proxy

v1.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: nginx-proxy/nginx-proxy@1.0.0...1.0.1

v1.0.0

Compare Source

What's Changed

Contributors

Many thanks to the following people for their work and/or feedback on the path based routing feature.
@​AlexanderLieret @​junderw @​warren-ru @​JMLX42 @​OliverRhyme @​trowj @​WolfspiritM @​rodrigoaguilera @​RafaelKr @​gregsymons

Full Changelog: nginx-proxy/nginx-proxy@0.10.1...1.0.0

v0.10.1

Compare Source

What's Changed

New Contributors

Full Changelog: nginx-proxy/nginx-proxy@0.10.0...0.10.1

v0.10.0

Compare Source

This is a minor release.

Bugs fixed:

  • #​1769 the DockerHub images had world writable files in /app (fixed by #​1770)

Changes since 0.9.3:

  • the DH group generation at startup has been removed and replaced by the use of pre-generated RFC 7919 DH groups (#​1797 #​1848)

Dependencies:

  • nginx -> 1.21.5

Other changes:

  • the container based test method (as opposed to running tests directly on the host) was fixed in #​1856.
  • various code style (#​1807) and docs update (#​1775 #​1819).

Thanks to @​crazy-max, @​kevinnls, @​polarathene, @​ucyang and @​HPPinata for their contributions to this release.

v0.9.3

Compare Source

This is a patch release.

Changes since 0.9.2:

  • the upstream names where reverted to the legacy (pre 0.9.1) behaviour to avoid breaking existing setups that rely on them. A new optional SHA1_UPSTREAM_NAME environment variable enable 0.9.2 behaviour if needed. See #​1736 for more information.

Default behaviour:

##### example.com
upstream example.com {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://example.com;
  }
}

With SHA1_UPSTREAM_NAME set to true:

##### example.com
upstream 0caaf24ab1a0c33440c06afe99df986365b0781f {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://0caaf24ab1a0c33440c06afe99df986365b0781f;
  }
}

Plus some CI and docs updates.

v0.9.2

Compare Source

This is a patch release.

Bugs fixed:

  • correctly redirect HTTP to custom HTTPS port using when using HTTPS_PORT (fixed by #​1662)
  • use a single server 127.0.0.1 down entry in upstream blocks, and only when required (fixed by #​1667, #​1679)

Changes since 0.9.1:

  • nginx 1.19.10 -> 1.21.1
  • docker-gen 0.7.6 -> 0.7.7
  • golang 1.16.5 -> 1.16.7

Various CI and docs updates.

Note:

  • in 0.9.1, the upstream names where changed and "-upstream" was appended to the bare reverse proxied hostname.
  • in 0.9.2, they were changed again to an sha1 hash of the hostname to prevent further issues with incorrect upstream names.

If you relied on those upstream names in your custom configuration(s), please be aware that you'll have to update them if you use version 0.9.1 or higher.

0.9.0 and prior:

##### example.com
upstream example.com {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://example.com;
  }
}

0.9.1:

##### example.com
upstream example.com-upstream {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://example.com-upstream;
  }
}

0.9.2+:

##### example.com
upstream 0caaf24ab1a0c33440c06afe99df986365b0781f {
  server 172.16.0.2:80;
}

server {
  server_name example.com;
  #[…]
  location / {
    proxy_pass http://0caaf24ab1a0c33440c06afe99df986365b0781f;
  }
}

v0.9.1

Compare Source

This is a patch release.

Bugs fixed:

  • #​1162 upstream naming pre-empts proxy-passing to other load-balanced services (fixed by #​1163)
  • #​1361, #​1407 and #​1512 bad parsing of the arguments passed to the DH parameters generation script (fixed by #​1263)
  • #​1424 nginx config load broken by resolver's IPv6 link local interface scoped address (fixed by #​1557)
  • X-Forwarded-Ssl header was improperly set in SSL-terminated setups (fixed by #​1185)
  • create_server_certificate.sh script in tests was broken (fixed by #​1619)
  • #​1132 upstream server was incorrectly marked as down when using internal networks (fixed by #​1609)

Changes since 0.9.0:

  • new SERVER_TOKENS per proxied container variable to control the server_tokens directive (#​1620)
  • additional debug information on the rendered template with the DEBUG variable (#​1609)
  • $upstream_addr added to nginx access logs (#​1659)
  • switch to a Go module compatible version of forego (#​1603)
  • golang 1.15.10 -> 1.16.5

Various doc updates.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/jwilder-nginx-proxy-1.x branch from c5feb02 to 9420894 Compare April 10, 2022 13:51
@renovate renovate bot force-pushed the renovate/jwilder-nginx-proxy-1.x branch from 9420894 to ca2a999 Compare June 20, 2022 12:39
@kasparsd kasparsd merged commit a248498 into master Jun 20, 2022
@kasparsd kasparsd deleted the renovate/jwilder-nginx-proxy-1.x branch June 20, 2022 12:45
@delawski
Copy link
Contributor

delawski commented Aug 9, 2022

It seems that this change breaks the boilerplate. On one of the projects, when trying to access the local environment, I kept getting a 502 Bad Gateway error.

@piotr-bajer found out that reverting this change (degrade jwilder/nginx-proxy to 0.9.0) fixes the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants