Merge pull request #30 from helio-frota/deps

fix: sec issues and dep updates adjustments

Author: helio-frota

blog/2023-02-13-elfsign.md

@@ -92,7 +92,7 @@ bit of care, handling a private key properly.
 
 Luckily, we now have [sigstore](https://www.sigstore.dev/). Sigstore can help us with two things, creating
 short-lived private keys (Fulcio), and a tamper-resistant log (Rekor). We already talked a bit about both in
-the context of [gitsign]({% post_url 2022-12-02-sign-commits-with-sigstore %}).
+the context of [gitsign](\{% post_url 2022-12-02-sign-commits-with-sigstore %\}).
 
 Adding Fulcio and Rekor to `elfsign`, we gain a bunch of cool things:
 
@@ -105,7 +105,7 @@ could also create something like `elfsign execute` to verify and execute, but th
 
 As we can prove, using Rekor, that we did own the private key during the time the certificate was valid, and we
 provided the signature/digest at the same time, we now only need to decide if we want to trust the issuer and the
-subject the certificate was issued for. And by storing [the Rekor bundle]({% post_url 2023-01-13-sigstore-bundle-format %}), we can do this offline too.
+subject the certificate was issued for. And by storing [the Rekor bundle](\{% post_url 2023-01-13-sigstore-bundle-format %\}), we can do this offline too.
 
 ## Too good to be true?
 

docusaurus.config.js

@@ -1,8 +1,8 @@
 // @ts-check
 // Note: type annotations allow type checking and IDEs autocompletion
 
-const lightCodeTheme = require("prism-react-renderer/themes/github");
-const darkCodeTheme = require("prism-react-renderer/themes/dracula");
+const lightCodeTheme = require("prism-react-renderer").themes.github;
+const darkCodeTheme = require("prism-react-renderer").themes.dracula;
 
 /** @type {import('@docusaurus/types').Config} */
 const config = {