bootstrapcdn fontawesome update to 5+ best practices?

I want to update to the latest fontawesome, because it has icons I want, such as iTunes and Patreon. The inclusion in my template is thus:
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">

Fontawesome uses a different URL, obvs:
<link href="https://use.fontawesome.com/releases/v5.0.7/css/all.css" rel="stylesheet">

Since bootstrapcdn is only supporting up to 4.7.0, can I use Fontawesome’s tag instead without major consequences? and if so, anything I should be aware of (i.e. would I need to fix anything else in the code)?

[Update: I tried substituting the fontawesome url, but the Patreon icon doesn’t appear. (However, the iTunes one does.) I must be missing something… Yes, I am using “fab fa-patreon”]

aTdHvAaNnKcSe
(THANKS in advance)

Have you tried to clear the browser cache? Both should work without any problem

@ki-themes thanks for your reply. I did manage to get it working, but unfortunately AMP does not validate when using the fontawesome stylesheet, and BootstrapCDN is stuck on v 4.7.0.

Any workarounds? Or do I just wait?

You can download the files and include them inside of the template

@ki-themes yes, great idea! Thank you.

[Update:] Sorry, but I’m getting exactly the same error. As I understand it, AMP only accepts certain sources for fonts (see link below). If I download and use the font inside my template, I’m just linking to a css stylesheet in a different (but still unacceptable) location. Am I missing something?

You may be missing something but I’m not sure what it is

I think I will have to go back to BootstrapCDN 4.7.0, unfortch, and just wait for an update. There doesn’t seem to be any other way to use Fontawesome with Amp validation. Thanks for your help.