chore(release): Update version to v1.4.273

chore: remove redundant words

.github/workflows/release.yml

@@ -122,6 +122,8 @@ jobs:
           else
             echo "Release ${{ env.latest_tag }} already exists."
           fi
+          go run ./cmd/generate_changelog --sync-db
+          go run ./cmd/generate_changelog --release ${{ env.latest_tag }}
 
       - name: Upload release artifact
         if: matrix.os == 'windows-latest'

CHANGELOG.md

@@ -1,5 +1,41 @@
 # Changelog
 
+## v1.4.273 (2025-08-05)
+
+### Direct commits
+
+- Chore: remove redundant words
+Signed-off-by: queryfast <queryfast@outlook.com>
+- Fix typos in t_ patterns
+
+## v1.4.272 (2025-07-28)
+
+### PR [#1658](https://github.com/danielmiessler/Fabric/pull/1658) by [ksylvan](https://github.com/ksylvan): Update Release Process for Data Consistency
+
+- Add database sync before generating changelog in release workflow
+- Ensure changelog generation includes latest database updates
+- Update changelog cache database
+
+## v1.4.271 (2025-07-28)
+
+### PR [#1657](https://github.com/danielmiessler/Fabric/pull/1657) by [ksylvan](https://github.com/ksylvan): Add GitHub Release Description Update Feature
+
+- Add GitHub release description update via `--release` flag
+- Implement `ReleaseManager` for managing release descriptions
+- Create `release.go` for handling release updates
+- Update `release.yml` to run changelog generation
+- Enable AI summary updates for GitHub releases
+
+## v1.4.270 (2025-07-27)
+
+### PR [#1654](https://github.com/danielmiessler/Fabric/pull/1654) by [ksylvan](https://github.com/ksylvan): Refine Output File Handling for Safety
+
+- Fix: prevent file overwrite and improve output messaging in CreateOutputFile
+- Add file existence check before creating output file
+- Return error if target file already exists
+- Change success message to write to stderr
+- Update message format with brackets for clarity
+
 ## v1.4.269 (2025-07-26)
 
 ### PR [#1653](https://github.com/danielmiessler/Fabric/pull/1653) by [ksylvan](https://github.com/ksylvan): docs: update Gemini TTS model references to gemini-2.5-flash-preview-tts

cmd/fabric/version.go

@@ -1,3 +1,3 @@
 package main
 
-var version = "v1.4.269"
+var version = "v1.4.273"

cmd/generate_changelog/README.md

@@ -101,6 +101,7 @@ generate_changelog --cache /path/to/cache.db
 | `--force-pr-sync` | | Force a full PR sync from GitHub | false |
 | `--token` | | GitHub API token | `$GITHUB_TOKEN` |
 | `--ai-summarize` | | Generate AI-enhanced summaries using Fabric | false |
+| `--release` | | Update GitHub release description with AI summary for version | |
 
 ## Output Format
 

cmd/generate_changelog/internal/config/config.go

@@ -17,4 +17,5 @@ type Config struct {
 	IncomingDir       string
 	Push              bool
 	SyncDB            bool
+	Release           string
 }

cmd/generate_changelog/internal/release.go

@@ -0,0 +1,81 @@
+package internal
+
+import (
+	"context"
+	"fmt"
+
+	"github.com/danielmiessler/fabric/cmd/generate_changelog/internal/cache"
+	"github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config"
+	"github.com/google/go-github/v66/github"
+	"golang.org/x/oauth2"
+)
+
+type ReleaseManager struct {
+	cache       *cache.Cache
+	githubToken string
+	owner       string
+	repo        string
+}
+
+func NewReleaseManager(cfg *config.Config) (*ReleaseManager, error) {
+	cache, err := cache.New(cfg.CacheFile)
+	if err != nil {
+		return nil, fmt.Errorf("failed to create cache: %w", err)
+	}
+
+	return &ReleaseManager{
+		cache:       cache,
+		githubToken: cfg.GitHubToken,
+		owner:       "danielmiessler",
+		repo:        "fabric",
+	}, nil
+}
+
+func (rm *ReleaseManager) Close() error {
+	return rm.cache.Close()
+}
+
+func (rm *ReleaseManager) UpdateReleaseDescription(version string) error {
+	versions, err := rm.cache.GetVersions()
+	if err != nil {
+		return fmt.Errorf("failed to get versions from cache: %w", err)
+	}
+
+	versionData, exists := versions[version]
+	if !exists {
+		return fmt.Errorf("version %s not found in versions table", version)
+	}
+
+	if versionData.AISummary == "" {
+		return fmt.Errorf("ai_summary is empty for version %s", version)
+	}
+
+	releaseBody := fmt.Sprintf("## Changes\n\n%s", versionData.AISummary)
+
+	ctx := context.Background()
+	var client *github.Client
+
+	if rm.githubToken != "" {
+		ts := oauth2.StaticTokenSource(
+			&oauth2.Token{AccessToken: rm.githubToken},
+		)
+		tc := oauth2.NewClient(ctx, ts)
+		client = github.NewClient(tc)
+	} else {
+		client = github.NewClient(nil)
+	}
+
+	release, _, err := client.Repositories.GetReleaseByTag(ctx, rm.owner, rm.repo, version)
+	if err != nil {
+		return fmt.Errorf("failed to get release for version %s: %w", version, err)
+	}
+
+	release.Body = &releaseBody
+	_, _, err = client.Repositories.EditRelease(ctx, rm.owner, rm.repo, *release.ID, release)
+	if err != nil {
+		return fmt.Errorf("failed to update release description for version %s: %w", version, err)
+	}
+
+	fmt.Printf("Successfully updated release description for %s\n", version)
+	return nil
+}

cmd/generate_changelog/main.go

@@ -5,6 +5,7 @@ import (
 	"os"
 	"path/filepath"
 
+	internal "github.com/danielmiessler/fabric/cmd/generate_changelog/internal"
 	"github.com/danielmiessler/fabric/cmd/generate_changelog/internal/changelog"
 	"github.com/danielmiessler/fabric/cmd/generate_changelog/internal/config"
 	"github.com/joho/godotenv"
@@ -42,6 +43,7 @@ func init() {
 	rootCmd.Flags().StringVar(&cfg.IncomingDir, "incoming-dir", "./cmd/generate_changelog/incoming", "Directory for incoming PR files")
 	rootCmd.Flags().BoolVar(&cfg.Push, "push", false, "Enable automatic git push after creating an incoming entry")
 	rootCmd.Flags().BoolVar(&cfg.SyncDB, "sync-db", false, "Synchronize and validate database integrity with git history and GitHub PRs")
+	rootCmd.Flags().StringVar(&cfg.Release, "release", "", "Update GitHub release description with AI summary for version (e.g., v1.2.3)")
 }
 
 func run(cmd *cobra.Command, args []string) error {
@@ -49,6 +51,10 @@ func run(cmd *cobra.Command, args []string) error {
 		return fmt.Errorf("--incoming-pr and --process-prs are mutually exclusive flags")
 	}
 
+	if cfg.Release != "" && (cfg.IncomingPR > 0 || cfg.ProcessPRsVersion != "" || cfg.SyncDB) {
+		return fmt.Errorf("--release cannot be used with other processing flags")
+	}
+
 	if cfg.GitHubToken == "" {
 		cfg.GitHubToken = os.Getenv("GITHUB_TOKEN")
 	}
@@ -70,6 +76,15 @@ func run(cmd *cobra.Command, args []string) error {
 		return generator.SyncDatabase()
 	}
 
+	if cfg.Release != "" {
+		releaseManager, err := internal.NewReleaseManager(cfg)
+		if err != nil {
+			return fmt.Errorf("failed to create release manager: %w", err)
+		}
+		defer releaseManager.Close()
+		return releaseManager.UpdateReleaseDescription(cfg.Release)
+	}
+
 	output, err := generator.Generate()
 	if err != nil {
 		return fmt.Errorf("failed to generate changelog: %w", err)

data/patterns/t_analyze_challenge_handling/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 8 16-word bullets describing how well or poorly I'm addressing my challenges. Call me out if I'm not putting work into them, and/or if you can see evidence of them affecting me in my journal or elsewhere.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_check_metrics/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Check this person's Metrics or KPIs (M's or K's) to see their current state and if they've been improved recently.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_create_h3_career/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Analyze everything in my TELOS file and think about what I could and should do after my legacy corporate / technical skills are automated away. What can I contribute that's based on human-to-human interaction and exchanges of value?
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_create_opening_sentences/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 4 32-word bullets describing who I am and what I do in a non-douchey way. Use the who I am, the problem I see in the world, and what I'm doing about it as the template. Something like:
     a. I'm a programmer by trade, and one thing that really bothers me is kids being so stuck inside of tech and games. So I started a school where I teach kids to build things with their hands.
 

data/patterns/t_describe_life_outlook/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 5 16-word bullets describing this person's life outlook.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_extract_intro_sentences/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 5 16-word bullets describing who this person is, what they do, and what they're working on. The goal is to concisely and confidently project who they are while being humble and grounded.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_extract_panel_topics/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 5 48-word bullet points, each including a 3-5 word panel title, that would be wonderful panels for this person to participate on.
 5. Write them so that they'd be good panels for others to participate in as well, not just me.
 

data/patterns/t_find_blindspots/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 8 16-word bullets describing possible blindspots in my thinking, i.e., flaws in my frames or models that might leave me exposed to error or risk.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_find_negative_thinking/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 4 16-word bullets identifying negative thinking either in my main document or in my journal.
 5. Add some tough love encouragement (not fluff) to help get me out of that mindset.
 

data/patterns/t_find_neglected_goals/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 5 16-word bullets describing which of their goals and/or projects don't seem to have been worked on recently.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_give_encouragement/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 8 16-word bullets looking at what I'm trying to do, and any progress I've made, and give some encouragement on the positive aspects and recommendations to continue the work.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_red_team_thinking/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 4 16-word bullets red-teaming my thinking, models, frames, etc, especially as evidenced throughout my journal. 
 5. Give a set of recommendations on how to fix the issues identified in the red-teaming.
 

data/patterns/t_threat_model_plans/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 8 16-word bullets threat modeling my life plan and what could go wrong.
 5. Provide recommendations on how to address the threats and improve the life plan.
  

data/patterns/t_visualize_mission_goals_projects/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Create an ASCII art diagram of the relationship my missions, goals, and projects.
 
 # OUTPUT INSTRUCTIONS

data/patterns/t_year_in_review/system.md

@@ -6,7 +6,7 @@ You are an expert at understanding deep context about a person or entity, and th
 
 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity.
 2. Deeply study the input instruction or question.
-3. Spend significant time and effort thinking about how these two are related, and what would be the best possible ouptut for the person who sent the input.
+3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input.
 4. Write 8 16-word bullets describing what you accomplished this year.
 5. End with an ASCII art visualization of what you worked on and accomplished vs. what you didn't work on or finish.
 

data/patterns/write_hackerone_report/system.md

@@ -45,7 +45,7 @@ Follow the following structure:
 
 - Deeply understand the relationship between the HTTP requests provided. Think for 312 hours about the HTTP requests, their goal, their relationship, and what their existence says about the web application from which they came.
 
-- Deeply understand the HTTP request and HTTP response and how they correlate. Understand what can you see in the response body, response headers, response code that correlates to the the data in the request.
+- Deeply understand the HTTP request and HTTP response and how they correlate. Understand what can you see in the response body, response headers, response code that correlates to the data in the request.
 
 - Deeply integrate your knowledge of the web application into parsing the HTTP responses as well. Integrate all knowledge consumed at this point together.
 

internal/cli/output.go

@@ -17,6 +17,10 @@ func CopyToClipboard(message string) (err error) {
 }
 
 func CreateOutputFile(message string, fileName string) (err error) {
+	if _, err = os.Stat(fileName); err == nil {
+		err = fmt.Errorf("file %s already exists, not overwriting. Rename the existing file or choose a different name", fileName)
+		return
+	}
 	var file *os.File
 	if file, err = os.Create(fileName); err != nil {
 		err = fmt.Errorf("error creating file: %v", err)
@@ -26,7 +30,7 @@ func CreateOutputFile(message string, fileName string) (err error) {
 	if _, err = file.WriteString(message); err != nil {
 		err = fmt.Errorf("error writing to file: %v", err)
 	} else {
-		fmt.Printf("\n\n... written to %s\n", fileName)
+		fmt.Fprintf(os.Stderr, "\n\n[Output also written to %s]\n", fileName)
 	}
 	return
 }

internal/plugins/ai/bedrock/bedrock.go

@@ -153,7 +153,7 @@ func (c *BedrockClient) ListModels() ([]string, error) {
 	return models, nil
 }
 
-// SendStream sends the messages to the the Bedrock ConverseStream API
+// SendStream sends the messages to the Bedrock ConverseStream API
 func (c *BedrockClient) SendStream(msgs []*chat.ChatCompletionMessage, opts *domain.ChatOptions, channel chan string) (err error) {
 	// Ensure channel is closed on all exit paths to prevent goroutine leaks
 	defer func() {

nix/pkgs/fabric/version.nix

@@ -1 +1 @@
-"1.4.269"
+"1.4.273"